Re:“We have decided not to integrate the Dart VM into Chrome”
by spankalee on Wednesday March 25, 2015 @03:39PM
(#9265401)
How so? You can use Dart today and yesterday and tomorrow.
[ Parent
| on HN ]
Re:“We have decided not to integrate the Dart VM into Chrome”
by spankalee on Wednesday March 25, 2015 @06:34PM
(#9266479)
wycats: IE 10 and up, Safari 6 and up, Chrome, FF, Opera, last 2 versions.
Re:“We have decided not to integrate the Dart VM into Chrome”
by wycats on Wednesday March 25, 2015 @06:21PM
(#9266414)
In what browser?
Re:“We have decided not to integrate the Dart VM into Chrome”
by wstrange on Wednesday March 25, 2015 @06:33PM
(#9266472)
Chrome, Firefox, Safari and even IE!
All via dart2js
Re:“We have decided not to integrate the Dart VM into Chrome”
by nailer on Wednesday March 25, 2015 @08:21PM
(#9266994)
Sure but you can also use es7 today (which I did).
Re:“We have decided not to integrate the Dart VM into Chrome”
by axlprose on Thursday March 26, 2015 @12:52AM
(#9267882)
Yes, and even compared to ES7, Dart still fares rather well. Most people that doubt this seem to not have actually tried the Dart workflow and core libraries. The productivity gain from those two features alone makes it compelling against all other compile-to-js options, because what it brings to the table isn't just a fancy language with nicer syntax+semantics.
Re:“We have decided not to integrate the Dart VM into Chrome”
by nailer on Thursday March 26, 2015 @04:39AM
(#9268391)
The dart std lib, at least the DOM manipulation bits, are indeed nice.
OTOH: JS has the largest module system of any programming language ever, which also tends to make it pretty productive.