Google previews its Dart language

 

Clean break from JavaScript?

Google has revealed the first developer preview of a programming language it is targeting at the creation of structured web applications.

Details of Google's strategy for the language first emerged in a leaked internal memo that was published to the web about three weeks ago.

The memo detailed a "two-pronged strategy for the future of JavaScript". It said that JavaScript in its current form is not viable in the long-term.

Google suggested "evolving" JavaScript but also working on a "clean break" by pushing "for a new language that addresses core problems in JavaScript that can't be repaired easily or quickly".

The internal memo used the codename Dash to describe this clean break. It has since been renamed Dart.

Google Dart team software engineer Lars Bak said in a blog post today that the "class-based optionally typed programming language for building web applications" was made to feel "familiar and natural to programmers and thus easy to learn."

Bak said that Google wanted the code to offer high performance across browsers and environments and to support projects of all sizes.

"We believe Dart will be great for writing large web applications," he said.

The language preview and tools are available as open source, Bak said.

Copyright © iTnews.com.au . All rights reserved.


Google previews its Dart language
 
 
 
Top Stories
The True Cost of BYOD - 2014 survey
Twelve months on from our first study, is BYOD a better proposition?
 
Photos: Unboxing the Magnus supercomputer
Pawsey's biggest beast slots into place.
 
ANZ looks to life beyond the transaction
If digital disruptors think an online payments startup could rock the big four, they’ve missed the point of why people use banks, says Patrick Maes.
 
 
Sign up to receive iTnews email bulletins
   FOLLOW US...
Latest Comments
Polls
What is delaying adoption of public cloud in your organisation?







   |   View results
Lock-in concerns
  29%
 
Application integration concerns
  3%
 
Security and compliance concerns
  28%
 
Unreliable network infrastructure
  9%
 
Data sovereignty concerns
  21%
 
Lack of stakeholder support
  3%
 
Protecting on-premise IT jobs
  4%
 
Difficulty transitioning CapEx budget into OpEx
  3%
TOTAL VOTES: 1094

Vote