5 ms·
To be fair, repls can do much more than one line at a time. You just need a more capable editor than a line oriented prompt. This is not to detract from your
by taeric 9y ago
To be fair, repls can do much more than one line at a time. You just need a more capable editor than a line oriented prompt.
This is not to detract from your point. I have gone further and lamented the death of debuggers. Primarily because I have seen them used so rarely in the wild. That combined with the somewhat ironic rise of functional idioms in java that are actually difficult to debug. (My understanding from last time I asserted this, is just that I don't see them used much.)
- seanmcdirmid 9y agoMy experience is that when the debuggers are bad, they aren't used much, and when they are good, they are used all the time. The web browsers offer poor debugging experiences ATM, so for Javascript they aren't as useful as say debugging C# in Visual Studio or even Java in Eclipse. I agree that functional programming idioms in practice makes debugging harder, but only because debuggers lack the right UI to deal with the buried control flow of things like functional orgami. I've heard F# with its Visual Studio plugin is doing better in this regard.
- taeric 9y agoMy apologies, my point in "functional being harder to debug," was purely on some of the new idioms in Java. JavaScript has the advantage of the debugger keyword. Has the disadvantage of the execution engine not being hooked up to the editor for most folks. I have seen some changes to that. And I am still enamored with skewer mode. (Haven't used it much.) Java debugging blows my mind. It was trivial to do and I recall tons of people doing it in school. I have yet to see anyone at the last few offices I've worked in do it. Worse, many common designs and practices make it much more difficult than it needs to be.
- Sacho 9y agoUh, what makes you say web browsers offer poor debugging experiences? I'd put them about on par with Visual Studio's C# debugging, even better in some areas(Immediate Mode in VS breaks down often, the debugger craps out on some LINQ-to-X expressions, etc, whereas web browsers offer all the malleability of JS right there at the debug breakpoint).
- seanmcdirmid 9y agoChrome and Firefox devtools are very very behind in modern debug features, it’s like programming in the early 90s again! Not just that, but debugging is also extremely fragile, crashing often on small programs for no good reason. It can’t even call tostring automatically in the watch windows because JavaScript VMs have no easy way of quickly sandboxing those fine grained calls.
- Sacho 9y agoI'm not sure I understood the toString() issue you described here, and I don't recall encounting crashes with any particular regularity. What I do recall is having to deal with VS2017's inability to execute or watch many LINQ/lambda expressions which made certain debug sessions completely useless. The biggest issues I've had with web browser debuggers is the interaction(or lack thereof) between source maps and debugging. I don't know any of the modern debug features that the browsers are missing - could you mention some?
- taeric 9y agoMy guess is they are referring to Reverse Debugging[1] and similar features. Basically, being able to step backwards in the code. A feature not many realize exists already is "Restart Frame." I confess I always forget it exists in Chrome. It can get you close to "step backwards." I don't know if you can use it to redefine a function and start it over, though. (Something you can do in languages people love the debuggers of.) [1] http://sourceware.org/gdb/wiki/ReverseDebug http://sourceware.org/gdb/wiki/ReverseDebug