“We have decided not to integrate the Dart VM into Chrome”

Re:“We have decided not to integrate the Dart VM into Chrome” by wrsh07 on Wednesday March 25, 2015 @02:55PM (#9265124)

I definitely agree that the impact of dart on ES6+ is perhaps the best reason for its existence; however, I don't think it has outlived its usefulness yet.

That said, I also hope that they reevaluate their position in the world in a couple of years once Javascript has advanced down the road blazed by eg Dart and CoffeeScript.

[also, Dart can just be thought of as an abstraction for the language of JS, and what problem can't be solved by just another layer of abstraction? :P ]

[ Parent | on HN ]

Re:“We have decided not to integrate the Dart VM into Chrome” by rjbwork on Wednesday March 25, 2015 @03:01PM (#9265165)

>what problem can't be solved by just another layer of abstraction? :P

Too many layers of abstraction. :P

[ Parent | on HN ]

Re:“We have decided not to integrate the Dart VM into Chrome” by cpeterso on Wednesday March 25, 2015 @05:03PM (#9265900)

> Too many layers of abstraction. :P

Not necessarily! That next abstraction may enable you to simplify your implementation, carving out lower layers of abstraction cruft.

[ Parent | on HN ]