Analysis of Google Dart
An anonymous reader writes "Google's new language landed with a loud thud, causing lots of interesting debates about the best place to stick semicolons... An article [in InfoQ] ... looks at some of the less discussed features. Snapshots seem to bring something like Smalltalk images and allow instant startup of applications (something Java has spent the last 15 years not delivering). Isolates are like OS processes and communicate with message passing — and as the article suggests, can fix the problem of Garbage Collection pauses by splitting up the heap (sounds like Erlang). There's more, mostly about features that remove some dynamic behavior in order to make startup and code analysis easier. Maybe Dart is worth a second look?"
1 == false
Yeah, everything except for true evaluates to false.
Do you even lift?
These aren't the 'roids you're looking for.
Oh please,
Java (or more correctly; its user base) has been crying out for some sort of faster startup since the mid 90s. No other problem has done more to keep Java off the desktop that the very slow startup times. If Java applets started as quickly as Flash objects manage to then we would still be seeing Java implemented on major web sites. I could never understand why Java doesn't snapshot and cache a prelinked version of a class the first time it loads, if anything the JVM is getting slower - the demo Java Applets on my website take about as long to start up in 2011 as they did in 2000 but my computer is many times faster.
sheep.horse - does not contain information on sheep or horses.
Xbox Live much, bro?
Say I wanted to write ls in Java. Startup time would be very important to me. Having dived back into Java development recently the bloat is getting me down. Nobody does anything small, except on Android where Dalvik does some of the caching and optimizing instead of the normal Java runtime.
http://michaelsmith.id.au