News for hackers. Stuff that matters.

A comment on “We have decided not to integrate the Dart VM into Chrome”. Parent comment

Re:“We have decided not to integrate the Dart VM into Chrome” by nailer on Wednesday March 25, 2015 @02:43PM (#9265041)
ES7 has async/await. Coffee script has a tighter syntax despite being older than Dart. Typescript has optional types and is being used at both Microsoft and Google. Also: you don't think JS has libraries and mixins?
[ Parent | on HN ]
Re:“We have decided not to integrate the Dart VM into Chrome” by skybrian on Wednesday March 25, 2015 @03:20PM (#9265274)
How about: "ES7 will most likely have async/await when it's finished."

Sorry, using the present tense for things that will be in browsers years later (hopefully) is a common practice that's an issue with me. Let's stick with what people can actually use today.

Also, pointing to features people can use in different dialects of JavaScript is not really fair. Just about everything you can think of has been experimented with and probably deployed somewhere. It doesn't count unless it's all available in the same toolchain and can be used in a unified way while writing a single app.

[ Parent | on HN ]
Re:“We have decided not to integrate the Dart VM into Chrome” by bhouston on Wednesday March 25, 2015 @03:35PM (#9265372)
> Sorry, using the present tense for things that will be in browsers years later (hopefully) is a common practice that's an issue with me. Let's stick with what people can actually use today.

ES7 async/wait is available now via the ES7 polyfill Babel.js: http://babeljs.io/

There are a ton of polyfills available right now for ES6/ES7 features: http://kangax.github.io/compat-table/es7/

BTW I also think that the current state of aggressive polyfills is also influenced by Dart's compile to JS functionality. :)

[ Parent | on HN ]
Re:“We have decided not to integrate the Dart VM into Chrome” by skybrian on Wednesday March 25, 2015 @04:28PM (#9265701)
Comparing Babel.js to dart2js is fair. I'd be interested in hearing more about about how well it works in practice from people who use Babel.js for large apps. (Also, how does it compare to Typescript?)
[ Parent | on HN ]
Re:“We have decided not to integrate the Dart VM into Chrome” by spellboots on Wednesday March 25, 2015 @08:41PM (#9267069)
Anyone creating a new Ember.js application today is using babel by default. It works very well in my experience. I haven't used typescript however.
[ Parent | on HN ]
Re:“We have decided not to integrate the Dart VM into Chrome” by bhouston on Wednesday March 25, 2015 @08:54PM (#9267123)
I think with time Typescript and Babel.js are to be merged, if you through in Strong Script to the mix I guess you have the future of JavaScript.
[ Parent | on HN ]
Re:“We have decided not to integrate the Dart VM into Chrome” by have_humility on Wednesday March 25, 2015 @03:28PM (#9265319)
> Sorry, using the present tense for things that will be in browsers years later (hopefully) is a common practice that's an issue with me. Let's stick with what people can actually use today.

If that's the metric we're applying, Dart fares no better...

[ Parent | on HN ]
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.
[ Parent | on HN ]
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?
[ Parent | on HN ]
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

[ Parent | on HN ]
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).
[ Parent | on HN ]
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.
[ Parent | on HN ]
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.

[ Parent | on HN ]
Re:“We have decided not to integrate the Dart VM into Chrome” by kyllo on Wednesday March 25, 2015 @03:30PM (#9265335)
Typescript has optical types

What are optical types? I've never heard of this term and Google turned up nothing on it.

[ Parent | on HN ]
Re:“We have decided not to integrate the Dart VM into Chrome” by untog on Wednesday March 25, 2015 @03:33PM (#9265347)
100% sure it's a typo of "optional types".
[ Parent | on HN ]
Re:“We have decided not to integrate the Dart VM into Chrome” by hibbelig on Wednesday March 25, 2015 @04:23PM (#9265675)
How boring :-) I'd love to look forward to a language with optical types. I'm sure it's at least as interesting as operand overloading in Intercal.
[ Parent | on HN ]
Re:“We have decided not to integrate the Dart VM into Chrome” by hmsimha on Wednesday March 25, 2015 @05:10PM (#9265938)
Optical typing must be like duck typing taken to the extreme. If it looks like a duck then it's a duck, dammit!
[ Parent | on HN ]
Re:“We have decided not to integrate the Dart VM into Chrome” by girvo on Wednesday March 25, 2015 @08:28PM (#9267023)
Type coercion taken way too far ;)
[ Parent | on HN ]
Re:“We have decided not to integrate the Dart VM into Chrome” by kyllo on Wednesday March 25, 2015 @04:48PM (#9265821)
I was imagining something like Lens in Haskell :)
[ Parent | on HN ]
Re:“We have decided not to integrate the Dart VM into Chrome” by DonHopkins on Wednesday March 25, 2015 @08:47PM (#9267093)
Optical types are when they shave the bushy hair off of the type system, and it looks an inch longer.

https://www.youtube.com/watch?v=NsbXwzqlqsU

[ Parent | on HN ]
Re:“We have decided not to integrate the Dart VM into Chrome” by moron4hire on Wednesday March 25, 2015 @06:05PM (#9266290)
The types aren't optional. The types are always there. The type annotations are optional.
[ Parent | on HN ]