3 ms·
Exactly that. When Mozilla started reimplementing it, it seemed somehow error stack traces started breaking for both firebug and the horrible builtin developer
by unilynx 4y ago
Exactly that. When Mozilla started reimplementing it, it seemed somehow error stack traces started breaking for both firebug and the horrible builtin developer tools
That's when we switched to Chrome for debugging, and only come back to Firefox to debug endless loops and stack overflows (because their Javascript VM is still better at being able to suspend/trace those)
- bornfreddy 4y agoYup. It is quite incredible how many times Mozilla shot itself.
- hinkley 4y agoWell, Mozilla itself was the result of a failed attempt at a rewrite. Jamie Zawinski decided that being a bar owner was a better career option shortly after that experience. It’s hard to tell with autodidacts if they really got pissed off about something or just needed an excuse to deep dive into something completely unrelated, and I would definitely peg him as one.