Earlier quoted context omitted.
I think they're almost done with the first iteration of WebSocket support in the Firefox DevTools. Might even already be in Developer Edition: https://bugzilla.mozilla.org/show_bug.cgi?id=885508
Great news. This is the only thing I open chrome for! Thanks for the info.
Firefox 70 released for Firefox Quantum: Developer Edition
111–116 of 116 posts
Re: Firefox 70 released for Firefox Quantum: Developer Edition
#112Earlier quoted context omitted.
Other than the web socket support in Chrome, the FF dev tools are a billion times better than Chrome now. I cannot work without the css layout overlays from FF dev tools. Makes working with grid layouts insanely easy.
The Chrome profiler is a lot better (IMO) than the one Firefox ships. But then there is https://profiler.firefox.com/ The debugger/sources view in Firefox also seems buggier still. E.g. a lot of times while it correctly displays source-mapped locations in the console, clicking on those source links will not actually go to the right place in the source view (it will either end up in the packed source or it will not go…
Re: Firefox 70 released for Firefox Quantum: Developer Edition
#113Re: Firefox 70 released for Firefox Quantum: Developer Edition
#114What’s the Mozilla community like for external contributions? Before the big google dollars it seemed cliquey and now seems mostly paid people. Is that accurate ? I wonder what happens to Firefox if the search dollars run out and companies are uniting behind chrome/WebKit
I regularly watch commits from webkit, chromium, gecko-dev and servo. Webkit is developed almost exclusively by Apple (or more maintained because development is very slow, btw I suspect that Apple will drop webkit as it become too far behind) There are also a few igalia devs and one Sony dev + one Gmail dev. Chromium is developed by so many people, Google, Microsoft, opera, QT, hardware makers (ARM, Intel, nvidia), s…
If the web is going towards a Chrome monoculture, then perhaps Microsoft would step in to keep some competition in the marketplace.
Stranger things have happened!
Re: Firefox 70 released for Firefox Quantum: Developer Edition
#115Earlier quoted context omitted.
I saw a tweet recently about macOS power consumption fixes: https://mobile.twitter.com/pcwalton/status/11661937700160798... Haven't noticed any memory bloat myself though (= it consumes a lot of memory, like any browsers). It's somewhere between Safari and Chrome.
Random question: Do you use safari? Do you see significant performance differences with chrome? Do you see broken/partially broken websites on safari vs chrome ?
The thing is, Chrome actually feels snappier than both Firefox and Safari when I am using it, probably because it's profile is empty (almost no extensions, no history, etc.).
I rarely see broken websites, with any browser. And usually it's because of my ad-blocking extensions. Google websites are slower on Firefox, but rumours are saying that it's almost on purpose… (one more reason to not use Google products like Chrome).
Re: Firefox 70 released for Firefox Quantum: Developer Edition
#116I can't seem to make the switch away from Chromium devtools. I don't know whether it's because I am habituated to the Chromium ones or whether there is something klunky about the Firefox devtools that I can't put my finger on.
As others have pointed out, it may be worth looking into whether or not your reasons for using Chromium for the devtools are simply habit. Speaking for myself, I'm in the other camp. I never really ditched Firefox for Chrome except for a brief period[0]. I returned to Firefox back when it was still called "Firefox (Not Responding)". Other than the renaming (/s), it -- generally -- flies. The devtools do what I need t…
After deciding that life's too short and that I really should give it a try - I've found out that source maps doesn't work on Firefox's dev tools. Back to chrome.