4 ms·
I see at least two problems: - debugging such code is a nightmare(node.js itself makes it hard enough) - static analysis of such code is not possible.. yet?
by dotborg 14y ago
I see at least two problems:
- debugging such code is a nightmare(node.js itself makes it hard enough)
- static analysis of such code is not possible.. yet?
JS and programmers should target Java-like experience imo, static analysis, code assist, dependency check - all of it performed on-the-fly. We won't get it by creating yet another layer above main language, because IDE vendors simply can't cope.
- jlongster 14y agoJavascript is a dynamic language. And especially one that is difficult to do static analysis on. We get much more out of macros than we would with some attempts at static analysis, when it comes to programmer productivity in the end.
- dotborg 14y agoproblem of static analysis in JS code is difficult, yet it's worth to solve, coolness of JS and safety of static analysis, that would be great macros are just lame workaround:)