So, apart from the vacation part, pretty much the same as renting privately in the UK then.
614 karma · joined August 10, 2010
So, apart from the vacation part, pretty much the same as renting privately in the UK then.
Agreed that getting out of the USD hegemony is inevitable. As to whether it will be an orderly transition, I'd say that is far from assured, especially in the UK.
[0] http://en.wikipedia.org/wiki/List_of_countries_by_external_d...
What I took GP to mean, and indeed what Yegge's Grok appears to aim for, is the need for a universal modelling framework 'standard' for languages, tools and runtimes. Some kind of equivalent to LLVM but in the 'other direction' for modelling language semantics instead of code. Once a tool (e.g. editor) implements that standard it is able to 'plug in' to any tooling that also implements the standard. Potentially eliminating huge amounts of duplicated effort for tool makers etc.
I've long wanted to see something like an Eclipse daemon offering tool support to external editors etc. Ensime [1] does something along these lines, getting Scala' compiler functionality into Emacs using the Swank protocol from Slime [2].
http://bsumm.net/2012/08/11/steve-yegge-and-grok.html
http://www.youtube.com/watch?v=KTJs-0EInW8
HN discussion: https://news.ycombinator.com/item?id=4371267
...and for once common sense seems to have been enacted. Props to Alsup and the EU court for this :-)
The spirit of Borland still lives:
http://en.wikipedia.org/wiki/Lotus_Dev._Corp._v._Borland_Int....
This post has more on the story and Mueller has not denied it's veracity:
http://paidcontent.org/article/419-is-patent-expertblogger-f...
"He says that he and Microsoft have worked together more than once, but that because of a confidentiality agreement with the company, he can’t elaborate on the details of that relationship."
Mueller buries his bias and sensationalism amongst otherwise insightful analysis. He also offers no opportunity for rebuttal on his blog (comments are always disabled).
https://plus.google.com/117117878292459457922/posts/hX2AZup1...
Additionally Cliff points out that there really needs to be some kind of standard CPU/Socket affinity API for VMs so that the relevant threads can share L3/L2 cache and reduce bus saturation. The Managed Runtime Initiative [2] is an interesting early effort to address this and other VM common concerns.
Edit: Looks like memory latency (not bus saturation) is the big issue if producer and consumer threads end up on different CPU sockets, hence Cliff's call for an explicit CPU/socket affinity API.
[1] http://www.azulsystems.com/blog/cliff/2011-09-23-a-pair-of-s... (scroll down to Disruptor section)
Only the other day patent 'analyst' Florian Mueller disclosed funding from Microsoft to write a report on FRAND licensing. He then subsequently admitted that he and Microsoft "...have worked together more than once, but that because of a confidentiality agreement with the company, he can’t elaborate on the details of that relationship..." [1].
Microsoft never really changed their spots, they just switched tactics.
[1] http://paidcontent.org/article/419-is-patent-expertblogger-f...
While switching to immutable state and using things like STM can help in many ways in order to program all these cores that we are getting thrown at us, we pay with the memory bandwidth costs. Doing this stuff on the JVM surely makes the problem worse.
As VMs as well as multi-core and functional style become more popular I can't help feeling we need typical memory bandwidth of new systems to grow a bit faster.
"I have to agree that my carrier is more to blame than Google or Android. After all, the facebook app isn't in the android source tree. It was introduced and locked in by my carrier.
My grippe is more about Android being touted left and right as a the first Open mobile platform while when it reaches the end user it's been locked by the carrier.
But indeed, my diatribe should have been more targeted to my carrier."
He's got a blog post here with some initial performance tests:
http://weblogs.java.net/blog/forax/archive/2011/09/04/hotspo...
Looks really fast when using type annotation (edit: faster than Java?!). Interestingly he is using the upcoming -hsx Hotspot server flag which makes a big difference in speed.
Possibly this is falling victim to overzealous flagging as people go through the list.
Keep on posting Colin, I often find the stuff you post here on HN to be interesting to me.
I'd love to see Gerry Sussman's talk from Strangeloop this year, does anyone know if a video is likely to be available at some point?
From what I can see there's been no talk relating to Scala and the challenges it has overcome and/or faces regarding its use of the JVM. Maybe, for now it has all been said and Scala is happily ploughing forward.
I read recently a quote from Martin Odersky [1] claiming that the virtual extensions methods (aka public defender methods) proposed by Brian Goetz et al comes tantalisingly close (but not quite) to allowing Scala to drop some of its class bloat from its libraries and runtime. It'd be great to see some Scala guys doing some talks on this kind of thing. Perhaps they're all busy covering the other conferences right now.
Similarly I don't see any representatives in the Project lambda mailing list speaking up for Scala's interests with regards to the changes to the JVM that need to be decided for Java 8. I'd hate to see comments and suggestions being made towards accommodating Scala but being rejected since its too late in the game w.r.t. Java 8. From what I can see opportunities to affect the JVM's evolution don't happen often.
I'm sure Martin et al are doing what they feel is necessary, it would be nice to be able follow the progress somewhere though!
[1] http://www.infoq.com/interviews/martin-odersky-scala-future
Can you share any more details on the user space situation? Will there be Xorg/Mesa/Gallium support? Will you be relying on Broadcom's driver team for updates, if any, or do you guys have driver source under NDA with which you can support the GPU in future?
This seems to be the biggest concern for many who are looking at the platform. Just trying to gauge what kind of useful lifespan this board will have with regards to keeping an up to date Linux distro running on it. There's going to be a lot of flux and ABI changes ahead in the Linux graphics stack. Some more GPU details on your Wiki would be great if you have them available.
Amongst other things it looks like Paul Phillips (a.k.a extempore) has done a lot of optimisation work. This looks like a pretty important one:
https://codereview.scala-lang.org/fisheye/changelog/scala-sv...
System scripting in Scala suddenly got a lot more appealing :-)
That sounds like you have just described pretty much any user facing computer ever built. Can you explain how this narrows the claims of the patent in any significant way?
if (freedom.outlawed())
assert !outlaw == !freeAlso will infuriate your co-workers and family members when they come to borrow your machine!
Very true. I'd say that writing out by hand works best, as opposed to typing it though.