I wish FF performance was as good as it is on Windows.
As much as I want to like Mozilla, even with Quantum, there's pretty much no hardware acceleration at all, missing out on potentially big performance benefits.
As others mentioned, e.g. VDPAU has been available for a long time now and there's no excuse for not taking advantage of GPU acceleration.
Now contrast this to evil Google and Chrome.
Firefox: https://imgur.com/mvtDenC Chrome: https://imgur.com/HBOpucc
Implying that it wasn't deliberately disabled. HW acceleration on Linux isn't enabled by default, and for good reason. Until those underlying reasons are changed, Linux does have a hardware-acceleration-on-Firefox problem.
I'll give it another chance in a couple of weeks, and hope that there will be a bypass that will force my outdated addons to work.
This is a good thing, and it's just a shame that so many addons haven't been updated yet.
however I've just ran nightly and although it says vimfx will work as a legacy plugin it's not working, so the deal's off. I shall not use my mouse!
Though losing Electrolysis will defeat one of the main benefits of running Firefox 57...
Other than a couple that were useful but ultimately not that important, and a couple I can do without until they get updated eventually, I managed to find that most of my Legacy extensions do have updated versions out. Namely, Video DownloadHelper and Greasemonkey, both extensions I thought would die with Firefox 57 out. That said, I wouldn't have known if I hadn't looked at the add-ons site as near as I can tell, while they still say "Legacy" in my Add-ons tab, they do have separate releases on the add-ons site specifically for Firefox 57 which are incompatible with my current browser and I'll probably have to install them again when I do update.* Assuming that is the case, you might find a decent chunk of that 70% already ready and you just have to take some extra steps to get them working again.
Overall, I am optimistic, lots of people have lots of nice things to say about 57 and the extensions situation is not looking nearly the sort of bad I was first expecting. I'm sure I've had more painful wait periods for my extensions going back almost a decade ago as it seems I really am waiting on just one and that one is coming shortly. Even those extensions which are now unsupported actually seem to have decent replacements and I've switched them over already.
* Note, this portion is entirely speculative, refer back to my commentary on waiting till an updated NoScript comes out before I actually install Firefox 57. It's possible they would just update once I do upgrade to 57 rendering my subsequent speculation entirely wrong.
Chrome is not open-source. Chromium is, but Chrome is not.
Mozilla Corporation is wholly owned by the non-profit.
> both are open source
Not to the same degree, as Chrome != Chromium
In contrast, when you sign into Chrome, "Your experience in other Google products is personalized by including your Chrome history with your Web & App Activity."(https://support.google.com/chrome/answer/185277)
But if a substantial portion of Mozilla's funding comes from an organisation that does have a profit motive to monitor and monetise my activity on the web, then surely that's almost as bad (for me as the end user)?
- If you do frontend work, our CSS grid inspector is unparalleled https://developer.mozilla.org/en-US/docs/Tools/Page_Inspecto...
- Firefox has built-in tracking protection (https://nakedsecurity.sophos.com/2017/11/12/firefox-to-offer...)
- Powerful add-ons like Tree Style Tab make managing large numbers of tabs much easier (https://addons.mozilla.org/firefox/addon/tree-style-tab/)
- Our WebAssembly performance tends to be better
- We should have better resource utilization when you have many tabs open
- You can mute audio on a page clicking the little speaker icon in the tab
If you want to contribute to the DevTools themselves, they're built using standard web technologies: HTML/JS, React/Redux, etc. https://github.com/devtools-html/
Although I don't know if chrome has this on by default nowadays as I turned it on so long ago.
But mute audio on per tab via speaker icon is available in chrome as well.
in chrome://flags/
* Tab audio muting UI control
If enabled, you can mute/unmute per tab via doing same thing.
(And I will have to find appropiate replacements for Leechblock and FireGesture)
https://addons.mozilla.org/en-US/firefox/addon/leechblock-ng...
Short of being able to optimize it soon, perhaps you could try buffering and displaying it at once. It would look less clunky and flimsy.
That said I'm giving FF57 a run as my main browser, will keep using Chrome Dev Tools for now.
https://superuser.com/questions/1261660/firefox-quantum-ver-...
(basically, hacking some CSS rules by creating a file in your AppData directory, so that the top bar is hidden)
Incidentally, I also discovered that Tree Style Tab's settings page under Firefox has a nice little box where you can configure the CSS it uses, which was nice because I prefer it with a smaller font and less padding.
Is there a way to selectively unblock certain trackers on a specific page?
I currently have the Tracking Protection set to Always and the block list on Strict. No problems yet, but I know there will be a few sites which won't correctly. Previously I always used Ghostery and there was a nice option to view exactly how many and which trackers were being blocked on each page. When viewing the blocked trackers, they could be selectively unblocked one at a time if required. This was handy to make some embedded video work, without necessary enabling Facebook tracking, which would occur if the whole page was unblocked.
I wish I had the time. So I'll have to wait for someone else to add the element DOM properties tab in thr panel that has the style rules and layout. Firebug had it, Chrome has it.
The right click and then Show DOM Properties with the results in the console pane is just painful to use.
Always watch where the incentives run, Chrome is for Google's best interests, not the web's and not the user's. Always has been and always will be because it's a for-profit organization.
Tab containers are useful for having multiple accounts on the same site (Gmail/Github), or isolating work or most secure sites from regular browsing. The containers are more light-weight and more general than Chrome profiles (and they don't depend on having external accounts).
Pinned tabs don't close on Command+W. It's a small thing, but I kept accidentally closing my pinned tabs in Chrome.
Chrome Dev Tools are hard to beat, although Fx is slowly catching up there, too. I don't mind launching Chrome just for web dev.
They were! I think they've shrunk, though that might be an optical illusion... And I can't see a simple way to make them bigger (simple as in: not editing the css file).
Or the Sco Linux lawsuits.
https://blog.mozilla.org/blog/2017/11/14/firefox-features-go...
The real world is not Star Wars. For all the privacy considerations etc., this comment above reads extremely naive.
https://winaero.com/blog/wp-content/uploads/2017/11/firefox-...