Re:Introducing the Firefox debugger.html
by renke1 on Wednesday September 14, 2016 @12:50PM
(#12498862)
Saving changes may be a bit harder these days with all the transpiling going on.
[ Parent
| on HN ]
Re:Introducing the Firefox debugger.html
by BinaryIdiot on Wednesday September 14, 2016 @02:26PM
(#12499867)
That's something the community will simply have to deal with. Transpiling already creates issues when you're debugging code since what you debug is different than what you wrote. Honestly this is one of the biggest issues I have with transpiling everything; you don't have to transpile even though our industry seems to be standardizing on it.
Re:Introducing the Firefox debugger.html
by revelation on Wednesday September 14, 2016 @04:56PM
(#12501149)
That's because integrated debuggers are a rather crass design error.
Windows doesn't come with a debugger. Linux doesn't come with a debugger. The JVM has no right-click launched debugger. CPython doesn't jump you into an interactive debug console. But all of those have a debug interface.
Leave building debuggers to others who have a clear picture of how they are using your platform.
Re:Introducing the Firefox debugger.html
by Chyzwar on Wednesday September 14, 2016 @08:35PM
(#12502508)
Linux and windows comes with multiple different debuggers.
Linux comes with strace, kdb, kgdb. You also have gdb by virtue having C compiler.
Only by tight integration with VM/compiler you can get decent debuggers. For example Smalltalk debuggers are class above to what JS can offer today. Crass design error is ignoring debugging needs until it is too late. Adding needed hooks and state managers is expensive, just look how much effort it is now: https://bugzilla.mozilla.org/show_bug.cgi?id=1207696