3 ms·
Frankly: speed. As a web developer it notice it all the time. Chrome (using Canary) is faster in every aspect; Firefox renders slowly, becomes unresponsive over
by cygned 10y ago
Frankly: speed. As a web developer it notice it all the time. Chrome (using Canary) is faster in every aspect; Firefox renders slowly, becomes unresponsive over time, hangs often when using web sockets (webpack); the developers tools seem to have problems with large files and so on.
I actually love Firefox' dev tools and I really would like to use it - and it's not a bad browser at all- but as a developer all the small things add up (same reason why I cannot use Safari as my daily browser).
- mythmon_ 10y agoI think the problem with webpack isn't the websockets, but that the devtools have a hard time dealing with large JS files, and especially large JS source maps. Changing the sourcemap option in webpack has helped avoiding hanging for me in the past. It would be nice if that wasn't the case though.
- cygned 10y agoWe use eval because we have around 60k LOC now and they were just too slow. The hanging occurs if you reload the page, it hangs a few seconds, then a message concerning websockets pops up in the dev tools and then the page reloads.