Google apparently thinks parts of Javascript kinda suck because they’re now working on a new web programming language called Dart that’s meant to remedy and simplify the more problematic aspects of the coding process.
Dart is being designed as a programming language that’s easy enough for any programmer to pick up and run with, but powerful enough to scale up to massive projects. Currently in an early preview mode, the language runs one of two ways: in a virtual machine, or as an app that’s been compiled and translated to Javascript. CNET says that they plan to directly incorporate the language into Chrome as well.
While Google isn’t directly saying that this is a Javascript competitor, the fact that they’re calling this a new programming language and not a supplement to Javascript, seems to indicates that they’d like for Dart to someday compete directly against the standard. [Dart via Google Code via CNET]
Blake
Tuesday, October 11, 2011 at 9:41 AMI wonder it’ll cause as little impact as their last language ‘Go’ http://en.wikipedia.org/wiki/Go_%28programming_language%29
Bloomy
Tuesday, October 11, 2011 at 11:04 AMAnother new language? Ok, but is it necessary?
I just read the Dart website. It looks like the conversion to javascript is an option.
There are three ways to use Dart:
1. run with a virtual machine (like java does)
2. translate it into javascript so it can be used by a browser
3. execute dart in a browser window directly (either in an HTML page, or a special Dart window called Dartboard) (this assumes the browser supports it. That would mean a new MIME type and opens up a whole slew of new security questions!!!)
I’m no programming expert, though I did have many years in COBOL, and dabble a little in C. Whats wrong with Java? Can anyone comment on what advantages Dart has over Java or Javascript?
Sabsy
Tuesday, October 11, 2011 at 7:09 PM“Dartboard”? [groans]
Yay, *another* language to run in the browser. Maybe instead of a new language, it’s time for a new paradigm? If JavaScript still runs like a dog after all the recent advancements in browser implementations, I can’t see it being an issue with the language.