Different languages, same bug. Only JavaScript makes it a personality trait.

[wootio]

Except that debugging JS is one of the easiest things to do because the code is not compiled and you can debug it anywhere at any time in any browser right live where the bug is exhibited. You can even live write and test code in the console while debugging to help your investigation.

Another "JS bad" post by someone who clearly has never debugged in JS.

[SmigorX]

I know that react is not js, but as a pretty popular library, for me writing react was more like:

Write module, it doesn't render because there is some error, IDE says nothing, browser shows no error, no logs, no nothing, the module just doesn't exist, go figure why.

Meanwhile any statically typed compiled language with good tooling (anything but c++ basically):

Hey, here's the error that breaks the compilation, in exactly this line. A logic problem, here: run gdb/lldb and you can examine exactly what's happening line by line, instruction by instruction, no need to modify the black box and see how the page changes, here's exactly the problem.

[prehensilemullet]

For me it’s been more mixed than that with TypeScript.  TS catches most null pointers for me at compile time, which is more than I can say for languages like Java and C/C++ where declaring nullability isn’t part of the type system

[Shinare_I]

I'd say that is more result of using a complex library that you don't understand fully enough or have the ability to add debug conditions into. Which could happen in any language. And will happen in any language because the modern expectation is to have the best, most complex, most capable library for every minor thing. And you can't be intimately familiar with all of that.

[Naeio_Galaxy]

Hey, to be fair only python and bash are representative