Dart 1.0 Released 121
stoolpigeon writes "Yesterday marked the release of Dart SDK 1.0, a cross-browser, open source toolkit for structured web applications. The Dart SDK 1.0 includes everything you need to write structured web applications: a simple yet powerful programming language, robust tools, and comprehensive core libraries. The language has been somewhat controversial, but Google continues to move it forward."
Reader slack_justyb adds some more detail: "The new release brings a much tighter dart2js compiler reducing overall JavaScript output up to 40%; Dartium — a version of Google Chrome that has the DartVM in addition to the JavaScript VM as native to the browser; PUB, a package manager for Dart add-ons; and several favorite 3rd party plug-ins that now come out-of-box, in addition to a lot of work for Dart server-side tools that can work to automate server side tasks and help in the construction of web pages.
However Dart has many critics not only from the IE and Apple camps, as one would guess, but from the Firefox and Opera camps as well. In addition to the low adoption of Dart from third parties there are some asking where does Dart go from here? Especially considering that Google is one of the strongest pushers for EcmaScript 6."
And I'd learn to use it (Score:3, Insightful)
If I hadn't come to absolutely loathe and distrust everything Google does over the course of the last few years.
Re:And I'd learn to use it (Score:5, Insightful)
This is totally Microsoft's VBscript for the web, and NaCL is their ActiveX. They're taking their role as the new Microsoft too seriously...
Re:And I'd learn to use it (Score:2, Insightful)
Chrome is the new IE6. A site I maintain has dropped IE6, but has recently been required to make CSS tweaks to fix box and other layout issues with Chrome.
Re:Cross browser? (Score:4, Insightful)
I think your arguments are pretty valid and I am by no stretch of the imagination a pro-Dart guy, but I believe that the "cross browser" claim comes from the olden days of cross platform languages. C/C++ had (has, just in case the past tense is a really bad choice) cross platform compilers they take C/C++ code and compile it to a language that the target platform understands. For example, C to ARM/x86/amd64/MIPS... compilers.
So my guess here, and it is just a guess, is that Google is using the same rationale to justify calling this a "cross browser" language, because the compiler can turn Dart into a language that can be understood by other browsers, much like a C compiler can compile into different paltforms. Arguments about if that is an accurate equation are totally justified and most likely will ensue hereafter. I'm just tossing up a guess as to why Google felt like that was an accurate statement.
Why not python? (Score:1, Insightful)
Why don't they just put the python runtime sandboxed? Why create a new language? Why not Lua or Ruby? Why not all of them so I can choose? All these languages have run-times on most major platforms (except iOS because, you know, Apple). Can't each browser just come up with a way to sandbox the language and provide the hooks to the DOM?
But really, the main problem isn't even javascript. The REAL problem is the DOM, it sucks manipulating it at run-time. The DOM was made to build documents, not applications. We need some real desktop-like api for building applications that allows little boxes on the screen to open html documents.
Burned by GWT (Score:5, Insightful)
Re:Cross browser? (Score:4, Insightful)
It has nothing to do with ActiveX at all.
ActiveX is a fancy *dll, which has full access to the System.
Dart is a sandboxed, either by the JavaScript Engine or the Dart Engine.
Re:Burned by GWT (Score:2, Insightful)
*Citation needed
At a quick glance, it looks to me like there was a GWT release just today...
Re:Burned by GWT (Score:5, Insightful)
What? Do you mean 2.6.0 RC1? 2.6 looks to be more of a clean up of the 2.5.1 stuff rather than anything new. If anything the main thing that 2.6 brings is that they brought Java 7 into the picture. I wouldn't say that Google *has* abandon GWT, but they sure are making the common gestures of getting ready for a good old fashion keelhauling. [blogspot.com]
Now for just my opinion, GWT sucks. It's a messy looking API and lacks a ton of flexibility. For example, trying to implement custom UI for your web page is painful and totally unpleasant. More so than say making the same customer UI in Java Swing (which is pretty painful in of itself). In my opinion, and you my mod me down for it, is that anything that is worst to do in (insert framework here) than it is in Java should not exist.