3 ms·
I remember IE5-6 ? Where it only told you there was an error, and you had to figure out where yourself via alert("this is line 500") Being used to that I think
by z3t4 8y ago
I remember IE5-6 ? Where it only told you there was an error, and you had to figure out where yourself via alert("this is line 500")
Being used to that I think Chrome dev tools are amazing. I love that you get a call stack on every console.warn. All those console.log's can be removed in production via overloading or marking them as pure functions when minifying, as they will otherwise slow down the app. There's otherwise no cost to having extra info available in the dev console, besides Firefox debugger being terrible slow 100x slower then the Chrome console.
- tty2300 8y agoI wonder if this is the reason that js tends to fail silently or convert types whenever possible because debugging errors was just too hard.
- z3t4 8y agoI think Microsoft just didnt want you to develop in JS, but they where forced to support it.
- goto11 8y agoThis was Netscapes design. I would guess it was designed like that because it was the simplest way to handle error conditions. Initially JavaScript was very simple and didn't even have exception, so there was no way to report errors.