News for hackers. Stuff that matters.

A comment on Virtual DOM is pure overhead (2018). Parent comment

Re:Virtual DOM is pure overhead (2018) by galaxyLogic on Sunday May 19, 2019 @03:49AM (#19952049)
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.

[ Parent | on HN ]
Re:Virtual DOM is pure overhead (2018) by DonHopkins on Sunday May 19, 2019 @06:01AM (#19952466)
>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_Syste...

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_/ddtord....

https://github.com/PDP-10/its/blob/master/doc/debugging.md

[ Parent | on HN ]
Re:Virtual DOM is pure overhead (2018) by guipsp on Sunday May 19, 2019 @05:27AM (#19952375)
>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

[ Parent | on HN ]