4 ms·

>Just curious what the use case for not doing compilation is? I'll add another one - the code that comes out is the code that goes in. Remember the days of Cof

>Just curious what the use case for not doing compilation is? I'll add another one - the code that comes out is the code that goes in. Remember the days of Coffeescript and minimization before sourcemaps? When most of your work comes from maintaining a codebase being able to effectively debug your code is crucial and hitting an error in production that is only painfully traced back to development will quickly offset any advantage that framework gives you.

galaxyLogic 7y ago
I think this is the the big reason to prefer plain old JavaScript. Compilation is ok in Java etc. where you can still debug your Java-code. But with many of these JavaScript frameworks I don't think that is possible, is it? I would add that "debugger" is not mostly a tool for finding and fixing bugs. It is tool for code-understanding, giving you a "live view" of your code, for READING your (or someone else's) code in the order it executes.
- guipsp 7y ago
  >But with many of these JavaScript frameworks I don't think that is possible, is it? It is, and works pretty much out of the box nowadays
- DonHopkins 7y ago
  >I would add that "debugger" is not mostly a tool for finding and fixing bugs. It is tool for code-understanding, giving you a "live view" of your code, for READING your (or someone else's) code in the order it executes. Absolutely! I couldn't agree more. From the discussion about forking sub-processes from the shell: The compiler/assembler/disassembler/debugger should be built into the shell, just like ITS DDT at the MIT-AI Lab in 1969! ;) https://en.wikipedia.org/wiki/Incompatible_Timesharing_System https://en.wikipedia.org/wiki/Incompatible_Timesharing_Syste... https://dspace.mit.edu/handle/1721.1/6153 https://dspace.mit.edu/handle/1721.1/6153 https://github.com/PDP-10/its/blob/master/doc/info/ddt.33 https://github.com/PDP-10/its/blob/master/doc/info/ddt.33 https://github.com/PDP-10/its/blob/master/doc/_info_/ddtord.1462 https://github.com/PDP-10/its/blob/master/doc/_info_/ddtord.... https://github.com/PDP-10/its/blob/master/doc/debugging.md https://github.com/PDP-10/its/blob/master/doc/debugging.md

galaxyLogic 7y ago

I think this is the the big reason to prefer plain old JavaScript. Compilation is ok in Java etc. where you can still debug your Java-code. But with many of these JavaScript frameworks I don't think that is possible, is it? I would add that "debugger" is not mostly a tool for finding and fixing bugs. It is tool for code-understanding, giving you a "live view" of your code, for READING your (or someone else's) code in the order it executes.

guipsp 7y ago
>But with many of these JavaScript frameworks I don't think that is possible, is it? It is, and works pretty much out of the box nowadays
DonHopkins 7y ago
>I would add that "debugger" is not mostly a tool for finding and fixing bugs. It is tool for code-understanding, giving you a "live view" of your code, for READING your (or someone else's) code in the order it executes. Absolutely! I couldn't agree more. From the discussion about forking sub-processes from the shell: The compiler/assembler/disassembler/debugger should be built into the shell, just like ITS DDT at the MIT-AI Lab in 1969! ;) https://en.wikipedia.org/wiki/Incompatible_Timesharing_System https://en.wikipedia.org/wiki/Incompatible_Timesharing_Syste... https://dspace.mit.edu/handle/1721.1/6153 https://dspace.mit.edu/handle/1721.1/6153 https://github.com/PDP-10/its/blob/master/doc/info/ddt.33 https://github.com/PDP-10/its/blob/master/doc/info/ddt.33 https://github.com/PDP-10/its/blob/master/doc/_info_/ddtord.1462 https://github.com/PDP-10/its/blob/master/doc/_info_/ddtord.... https://github.com/PDP-10/its/blob/master/doc/debugging.md https://github.com/PDP-10/its/blob/master/doc/debugging.md