31–40 of 95 posts
Earlier quoted context omitted.
Time to switch to DDG! It's come a long way in just a few years. It's my daily search engine and I have never looked back in reget.
Ireland being the small country it is, I generally found the results to be mediocre last time I tried. Still I'll give it a few days and see how I go.
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 sma…
1) It is significantly slower. That's probably because multiprocess ("e10s") is not enabled (and I don't even know why). 2) Stable version still does not support touch scroll on Linux (only Developer version does). Also do not understand why.
Enable e10s
MOZ_USE_XINPUT2=1 firefox
dom.w3c_touch_events.enabled
Pure inertia. I'm going to change right now. Been meaning to do this for weeks. Just one change to one line in my i3 startup config and that will be that. Update: I'm back in Firefox. Already been nagged twice by Google to use Chrome.
Time to switch to DDG! It's come a long way in just a few years. It's my daily search engine and I have never looked back in reget.
1) It is significantly slower. That's probably because multiprocess ("e10s") is not enabled (and I don't even know why). 2) Stable version still does not support touch scroll on Linux (only Developer version does). Also do not understand why.
Personal favorite: 8-year-old bug that causes select options to render incosistently if there's a transform anywhere in the DOM above it. https://bugzilla.mozilla.org/show_bug.cgi?id=455164
The reasons I don't use Firefox are because I'm using a Chromebook, an Android device, or an iPad.
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 sma…
I 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.