81–90 of 162 posts
This is speculation: but JetBrains work on dart IDE, android releasing ART, I'm tempted to say we're 2 years out from seeing DART running on android. It makes sense from a business sense, have the option of running dart apps on android would free the platform from its java dependance.
The VM already works on Android (x86 and ARM - not sure about MIPS).
Just waiting for "Works best on Chrome" Silverlight and ActiveX have already shown the usefulness of proprietary enhancements. No thanks.
What exactly is proprietary about it? Browser vendors are free to integrate the VM into their products, and if they don't want to there is dart2js which is acceptable. This isn't even close to the situation presented by Silverlight, ActiveX and I feel like you're being duplicitous by comparing them.
That's a tremendous amount of effort and it is likely to reduce the performance of JavaScript. Cross-language GC, in particular, is really hard. See Filip Pizlo's message to webkit-dev on this subject (citing two recent papers), which is part of the reason that Dart support was shot down when Google proposed adding it to WebKit: https://lists.webkit.org/pipermail/webkit-dev/2011-December/...
Is there a downloadable reference manual for the language? I see book excerpts, but not a complete language reference.
I am a newbie in field of Web Development, and recently I felt in love with JavaScript, especially because of the sheer capability to write Client side and Server side code in same language. Thanks to Meteor.js, it made my bond with JavaScript even more stronger. But now with the buzz of Google Dart going around, I am afraid that, am I betting on the wrong horse? Is it the right to jump on Google Dart bandwagon? To b…
Learn Javascript. Dart is a dead end technology. ALL the committers are from Google and it is not an open standard which basically eliminates any chance that Mozilla/Apple will ever consider adopting it. And frankly with Apple dominating the mobile web without them any solution will never eventuate to anything.
It will get standardized in the not too distant future. [1]
> Apple dominating the mobile web
Huh? Android's market share is over 80%. iOS got about 13%. [2]
[1] http://www.ecma-international.org/news/Dart%20workshop.htm
[2] http://thenextweb.com/insider/2013/11/12/idc-android-hit-81-...
Earlier quoted context omitted.
There are at least two problems with adding the Dart VM: 1. Standards. The Dart VM is not part of any web standard, nor part of a spec that has interest from multiple vendors, so it should not be shipped in a standards-compliant browser. This is a matter of principle that most browsers agree on these days, see for example Google's Blink guidelines: http://www.chromium.org/blink#new-features 2. Effort. Adding a new VM…
As an alternative, just working on/sponsoring/begging for an asm.js target might be enough to equalize performance.
However, I think it would be fun to explore that direction! I'd be happy to collaborate with Dart VM people on that.
Earlier quoted context omitted.
What exactly is proprietary about it? Browser vendors are free to integrate the VM into their products, and if they don't want to there is dart2js which is acceptable. This isn't even close to the situation presented by Silverlight, ActiveX and I feel like you're being duplicitous by comparing them.
> Browser vendors are free to integrate the VM into their products, and if they don't want to there is dart2js which is acceptable. That's a tremendous amount of effort and it is likely to reduce the performance of JavaScript. Cross-language GC, in particular, is really hard. See Filip Pizlo's message to webkit-dev on this subject (citing two recent papers), which is part of the reason that Dart support was shot down…
The Dart VM is nice but its primary purpose right now is running the Dart compiler and in Dartium which is only used by developers. (You can use it for other things but the ecosystem isn't there yet.)
Earlier quoted context omitted.
What exactly is proprietary about it? Browser vendors are free to integrate the VM into their products, and if they don't want to there is dart2js which is acceptable. This isn't even close to the situation presented by Silverlight, ActiveX and I feel like you're being duplicitous by comparing them.
> Browser vendors are free to integrate the VM into their products, and if they don't want to there is dart2js which is acceptable. That's a tremendous amount of effort and it is likely to reduce the performance of JavaScript. Cross-language GC, in particular, is really hard. See Filip Pizlo's message to webkit-dev on this subject (citing two recent papers), which is part of the reason that Dart support was shot down…
This is a really good reason why dart2js exists and why so much effort has been expended in making it good.
However, I think that if Dart proves to be a compelling platform for developers I don't think it's out of the question for browser vendors to put some serious thought into integrating the Dart VM natively alongside JS.
After all, Google is going to be doing exactly that with Chrome/Chromium...
Earlier quoted context omitted.
Understood. I'd just question if it needed JS - if JS actually added to the UX and outweighed the considerable dev cost.
How on earth do you propose to implement client side functionality without JS ? The fact is that MANY people need to support IE6-8.
I personally built a single page application about 2 years ago that worked in IE8, thanks to jQuery and the ecosystem of the time. jQuery, jQuery UI, various plugins incl. jsTree & DataTables.
It flew in Chrome, Firefox and Opera, even then. In IE8 it was slow as hell. Event listeners were slow, ajax and parsing JSON was slow. Everything was crazy slow. The app felt lumpy and awful. And when I hit bugs, the developer tools just were not there.
I would never do this again.
I'd wager that for IE Deliver something usable for oldIE. There are many people that share this view. I suggest watching this talk on how the BBC deals with legacy browsers (9m 20s): http://www.youtube.com/watch?v=YfvMQ316hMU&t=00h09m20s
So if i get it right, the way "Google" sees the future, there is Go at the server side and Dart at client side (which is in fact JS). Am I wrong? I would expect Google, or at least, a team at Google, to take over NodeJS which is based on their V8 and expand it to universal server client language and libs. JS can be complied into go binaries after all, so why not letting people write apps using the same language. Let…
Go is a better C++.