Is there a downloadable reference manual for the language? I see book excerpts, but not a complete language reference.
Dart 1.0 Is Out
71–80 of 162 posts
Re: Dart 1.0 Is Out
#72I 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.
Re: Dart 1.0 Is Out
#73Psyched! See our HN post about our Dart app (Dart rocks) and our team's disappointment with not being included in the 1.0 announcement. https://news.ycombinator.com/item?id=6735044
Shameless plug!!
Re: Dart 1.0 Is Out
#74This 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.
What does ART have to do with Dart?
Re: Dart 1.0 Is Out
#75Earlier quoted context omitted.
It compiles to JavaScript. The VM and dart2js are MIT licensed. It's not the same situation.
And who is responsible for keeping the DartVM/Dart2JS behaviour in sync ? Google being the ONLY committers don't exactly have a motivation to.
Dart2JS will be the key thing that drives Dart adoption.
So, yeah, Google has a motivation to keep it up to date.
Re: Dart 1.0 Is Out
#76Earlier quoted context omitted.
Well, Dart will eventually work best on Chrome because of the Dart VM. There's nothing stopping Mozilla from adding the VM to Firefox, of course. Getting an additional 2x-4x performance boost would be great.
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.
Re: Dart 1.0 Is Out
#77So 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…
> 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?
Yes, you are, in fact, wrong. Google doesn't have so narrow a vision. Dart is server and client side (the native VM is, aside from a for-testing-only build, server-side only now.) But the client side isn't just Dart (or JS, in which Google has also invested heavily), its also C/C++, and other languages, hence PNaCl, which also just went into general release.
And, sure, Go is a server-side language that Google is putting energy into, but so is Dart. And I doubt their vision ends there, those are just a couple of the more visible active fronts.
> 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.
The existing NodeJS team is doing enough for server-side JS-on-V8, and its open source -- Google could throw more resources, but its probably not the best bang-for-their buck in terms of developing new technologies that might improve the options for the things Google is concerned about. Doing what other people aren't doing is a bigger win.
> Let alone I see no effort on their side bringing any of those language into the native world of Android
I've seen quite a bit about Dart on Android (though I think there are issues with building the current distribution.) Less on Go.
Re: Dart 1.0 Is Out
#78Earlier quoted context omitted.
And who is responsible for keeping the DartVM/Dart2JS behaviour in sync ? Google being the ONLY committers don't exactly have a motivation to.
Dart2JS will be the key thing that drives Dart adoption. So, yeah, Google has a motivation to keep it up to date.
Only until there is enough adoption for them to stop caring.
Re: Dart 1.0 Is Out
#79Just 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.
Re: Dart 1.0 Is Out
#80Would someone who knows HTML/CSS/RoR better of learning Dart or JS next?
Even if you use language X that compiles to javascript ,you still need to learn javascript, Or it's a bit like learning rails without understanding ruby.
You can do Rails to a fair extent without really knowing Ruby, and just fumbling through it with a bunch of gems and messy code. In some ways it can be the gateway to learning Ruby itself, if you were so inclined to do so.
For things like CoffeeScript, which are fairly thin layers over another language, I'd always advise to just learn JS first. Dart and Clojurescript though are so far removed from their compilation target that you don't really need to know the JS, as long as there's good library support for what you want to do. In the case of clojurescript the interop is so seamless that it puts the focus on learning the APIs, which is where the true complexity lies. Of course, and even more so with typing, you also have the compiler to back you up.