3 ms·
One of the early issues raised about Dart was that it's compiled nature would make it hard to debug and was against the open source (easy to hack) nature of JS
by robmcm 12y ago
One of the early issues raised about Dart was that it's compiled nature would make it hard to debug and was against the open source (easy to hack) nature of JS on the web.
These days JS is more or less compiled, at least the file you get in your browser is very different that what the developer saw.
This seems to improve the case of Dart and I wouldn't be surprised if we saw more languages that compile down to JS in the near future.
We already have ES6 down to ES5 http://addyosmani.com/blog/author-in-es6-transpile-to-es5-as-a-build-step-a-workflow-for-grunt/ http://addyosmani.com/blog/author-in-es6-transpile-to-es5-as...
- zevyoura 12y agoIn addition to source maps, which have largely eased the pain of this issue, there's also the Dartium[0] build of Chrome, which has a proper Dart VM. [0] https://www.dartlang.org/tools/dartium/ https://www.dartlang.org/tools/dartium/
- grifpete 12y agoWhy would the compiled nature of Dart make it hard to debug? Presumably you mean debug by someone other than the original developer?
- robmcm 12y agoThat and debugging the compiled JS assuming there was a bug in the compiler or a browser quirk the compiler hadn't worked around. This is me remembering the arguments not making it ;)