Re:Google Dart target: Chrome soon, other browsers someday
by sethladd on Tuesday December 17, 2013 @01:33PM
(#6922822)
Dart compiles to JavaScript, is open source, and is now in ECMA. The project has mostly Google engineers committing, but we also have plenty of open-source contributions.
asm.js is a compile target that takes C/C++ code and outputs lots of typed arrays, and a custom engine to interpret the asm.js "hints". It's an interesting way to get C code onto the web, but developers don't write asm.js code by hand. In contrast, Dart is designed to be written by developers. The similarity is that both asm.js and Dart want to enable faster experiences for users, but they take very different approaches.
Re:Google Dart target: Chrome soon, other browsers someday
by _greim_ on Tuesday December 17, 2013 @01:55PM
(#6922993)
I thought that asm.js would be a compile target for any language, not just C/C++. E.g. you could have dart2asm instead of dart2js.
Re:Google Dart target: Chrome soon, other browsers someday
by mraleph on Tuesday December 17, 2013 @06:01PM
(#6924613)
Unfortunately right now asm.js is an unsuitable target for any dynamically typed language with garbage collection, because you have to run your whole runtime system and a garbage collector as asm.js'ied code, which is not exactly what you want in terms of overhead. Asm.js is a target for anything that is statically typed and low-level (e.g. C).
Re:Google Dart target: Chrome soon, other browsers someday
by _greim_ on Tuesday December 17, 2013 @07:50PM
(#6925087)
Ah. Thanks for the info.
Re:Google Dart target: Chrome soon, other browsers someday
by masklinn on Tuesday December 17, 2013 @02:15PM
(#6923157)
As far as I understand, the semantics of asm.js make that not very interesting.
Re:Google Dart target: Chrome soon, other browsers someday
by Touche on Tuesday December 17, 2013 @01:45PM
(#6922906)
> The project has mostly Google engineers committing, but we also have plenty of open-source contributions.
How many within the first year of it's development?
Re:Google Dart target: Chrome soon, other browsers someday
by masklinn on Wednesday December 18, 2013 @03:22AM
(#6926449)
According to the history of the AUTHORS file (commits are not properly attributed in the repository, as far as I can see) there were 12 "external contributors" in the first year of dart (as a public project anyway): https://code.google.com/p/dart/source/browse/branches/bleedi...
Re:Google Dart target: Chrome soon, other browsers someday
by sethladd on Tuesday December 17, 2013 @02:04PM
(#6923070)
Good question, I'd have to run some queries. dart.googlecode.com and github.com/dart-lang are the two main locations. We receive more patches for the libraries and docs than we do for the VM. But we have received patches for dart2js (a fairly complicated bit of code).
Re:Google Dart target: Chrome soon, other browsers someday
by sampk on Tuesday December 17, 2013 @02:00PM
(#6923023)
asm.js amuses me.. so many useless layers, NACL is much more sensible. But oh well Brendan Eich wants to keep his bragging rights.
Re:Google Dart target: Chrome soon, other browsers someday
by pcwalton on Tuesday December 17, 2013 @02:03PM
(#6923060)
> asm.js amuses me.. so many useless layers, NACL is much more sensible. But oh well Brendan Eich wants to keep his bragging rights.
asm.js does not have Pepper, so I think it actually has fewer layers.
I'm also a fan of Mozilla's asm.js. It seems to have so much potential. As a full-time JS dev, I guess I'm easily impressed. I just wish the browser makers could get their heads together and agree on some way forward, instead of incrementally polishing the JS "turd."