Blog
permalinkDigg's optimized data streams
Digg just released a prototype of their optimized data streams. This this is pretty cool. It uses MIME multipart HTTP responses to return a stream of responses, dispatching each one as it comes in. Bugzilla has been using MIME multipart for a while, though only to serve a short “Bugzilla is searching for your bugs” message before returning the actual results.
The Evolution of a Web Technology
- Obscurity
- Relative obscurity
- Robert Scoble gets it
- The ?-erati get it
- The SEO and marketing “experts” abuse it and annoy everyone
- Oprah ?s on her show
- Soccer moms and your grandma try ?ing
- Charmin Ultra-Soft becomes your friend on ?
- Someone in the ? space gets bought
- Time passes
- Robert Scoble declares that ? is dead
Oracle buys Sun (but really MySQL and Java)
The news that Oracle bought Sun caught me off guard. I was moderately disappointed when they were courting IBM as a suitor, but I would have been more than happy if they had gone through with the deal. IBM understands open-source and has a proven track record in Eclipse.
The final word on Google Eclipse plugin OSX crashes
I’ve blogged about the subject of GWT JVM crashes far too much (here and here). This is, I hope, the final word on the subject. I spent some time disassembling the Google Eclipse plugin (did I agree not to do that in one of the EULAs? ;)) and discovered that they are launching the JVM without using the Eclipse infrastructure. This means that the JVM arguments are effectively hardcoded, except in one case where -startOnFirstThread is passed for OSX clients. For those interested, the buggy classes of note are GWTDeploymentParticipant and LaunchUtils.
AppEngine+Java+OSX "Invalid memory access" on deploy
UPDATE, Apr 19 2009: This does not fix all compiler crashes in Eclipse. This is only useful for the compiler crashes where an Eclipse JVM configuration is used. Please see my later blog post for a better fix and disregard this information.
This is the same error I hit before (see my earlier post), but it happens in Eclipse during the “deploy to AppEngine” phase. You’ll see it if you’ve got a project configured with a 1.6 JVM on the build path (even if your .class compatibility is set to 1.5). It’s not obvious how to fix this at first glance - I had to dig around to find the options that Eclipse passes to the JVM.