Re:Google Dart target: Chrome soon, other browsers someday
by sethladd on Tuesday December 17, 2013 @01:28PM
(#6922778)
Why wait for the VM when you can compile to JavaScript today?
[ Parent
| on HN ]
Re:Google Dart target: Chrome soon, other browsers someday
by pjmlp on Tuesday December 17, 2013 @01:57PM
(#6923007)
Because customers only request JavaScript and I don't want to debug code generated from tools.
Re:Google Dart target: Chrome soon, other browsers someday
by sethladd on Tuesday December 17, 2013 @04:58PM
(#6924257)
Have you tried to use source maps to help debugging? Plenty of compile-to-JavaScript languages support source maps, and even some CSS frameworks. Building complex/large apps without a compiler and tools is really difficult. GWT, Closure, TypeScript, Dart are all efforts to help developers build more interesting apps that scale. Building/compiling is just a natural step in the process, and source maps are a natural output of that process.
Re:Google Dart target: Chrome soon, other browsers someday
by pjmlp on Tuesday December 17, 2013 @05:11PM
(#6924344)
As I repeated here multiple times:
- customers request JavaScript written by humans, not tools. As it makes them easier to get "resources"
- source maps are only an option on a few desktop browsers, no fun testing generated JavaScript on specific browser issues
Re:Google Dart target: Chrome soon, other browsers someday
by masklinn on Tuesday December 17, 2013 @02:16PM
(#6923169)
Debugging of generated code has gotten leaps and bounds better in the past few years though.