Slashdot Mirror
Slashdot Asks: Have You Switched To Firefox 57?
Yesterday, Mozilla launched Firefox 57 for Windows, Mac, Linux, Android, and iOS. It brings massive performance improvements as it incorporates the company's next-generation browser engine called Project Quantum; it also features a visual redesign and support for extensions built using the WebExtension API. Have you used Firefox's new browser? Does it offer enough to make you switch from your tried-and-true browser of choice? We'd love to hear your thoughts.
I'm a longtime Firefox user, and I've been annoyed as anyone about the bone-headed UI decisions in past years. But there, at least, you could use add-ons to revert back to a sane user interface, restore the status bar, and the like.
But killing your core, essential feature that makes your product actually worth using over any other browser? Did some cruel time traveller come back in time to ruin Firefox from within or something - I can't see a motivation on the part of those who would do this.
Firefox updated itself to 57 and made tabs impossible to see again.
They broke that quite a while back, but before 57 you could use "classic theme restorer" to make them visible again. But 57 stopped it from working and there is apparently no fix.
So had to switch back to 56.
And then they also brag about a lie on their website "Set up Firefox your way. " when you cannot even set tab borders anymore.
Love it. Fast and fixes rendering issues I had in FF 56.
-=Lothsahn=-
I am probably in the minority here (this place loves to complain) but I love the update. The new GUI is great once I got used to it and set the Dark Theme, plus it is noticeably faster. As for extensions, most of the ones I use are supported, and the ones that didn't i discovered i either didnt need or had functionality replacements available in the browser now that I didn't realize since never looked.
I've been using Firefox "since it all began" (and Mozilla before then, and Netscape when that was the thing - yes, that's a long time ago). My primary reason for sticking with Firefox through thick and thin was the wide selection of addons, in particular those designed to guard privacy and clean up my web experience.
With the move to webextensions there was little left to distinguish between Firefox and Chrome. My main reservation wrt. Chrome was presumable lack of ability to programmatically control cookie access list (i.e. allow/session only/deny sites ability to set cookies from an extension). Authors of Firefox cookie manager extensions (such as Cookie Controller) stated that doing so is not possible in Chrome.
Finally, I figured I'd give it a try. Less than 20 minutes of searching helped me find an API to control cookies from a Webextension. I wrote my own (and put it up in Chrome "web store" - "Cookie ACL manager"), and we were in business shortly.
While doing that, found a few bugs (not critical but def. needing some attention) in cookie and site data handling. Reported these through Chrome bug reporting site and was positively surprised by developers actually reading and responding (and, hopefully, fixing them soon). By comparison, never got Firefox developers to fix anything.
So - I am sorry Firefox, it's been a good 20 years, but now we must part. Farewell.
For three reasons:
1. The core security/privacy functionality is built tightly into the browser by default: HTTPS upgrades, script control, ad blocking, fingerprint protection, etc. No add-ons and depending on third party developers for these vital functions needed.
2. It is the only browser company really doing serious innovation, and that gives it the best chance to actually challenge Google. Plus, how is Mozilla going to challenge Google when it once again depends on Google for almost ALL of its income?
3. Lighting fast and operates in an intuitive UI. I no longer need to mess with all the configurations I had to in Firefox to get it how I wanted it. Brave makes it super easy to toggle things on and off without sorting through an about:config to harden the browser.
https://brave.com/
I ask this question every time and I will ask it again. Produce some packet captures of Chrome exhibiting this behavior. I'm waiting.
Only the State obtains its revenue by coercion. - Murray Rothbard
The've been doing this since 2011. Mozilla has been quite content to shed any technical merit they had for almost any reason at all. It all started when they saw Chrome beginning to become successful, and immediately decided to emulate Google's development environment. They adopted Google's rapid release and versioning method on a project that was neither technically nor culturally suited for it. They broke extensions by the truck load with that little gem, and instead of slowing down and letting the extension system catch up, their solution was to write a script that automatically scanned their extensions and just disabled the ones which hadn't caught up yet. Then they went all hell bent on adopting major UI changes that were demonstrably unpopular by the majority of its user base. And if alienating the extensions authors wasn't enough, many of the UI changes destroyed themes on back-to-back-to-back releases. It reminds me of one of my country's more famous prime ministers who, when he realized he'd alienated half my country, proceeded to give them the finger from his seat on a train. That's Mozilla. They alienate users, and then the ones who have stayed loyal they give the finger to.
All of this was in an attempt at emulating Chrome's burgeoning success. The problem is, they never figured out... you simply cannot surpass someone else by playing copycat on their methods. All they did was alienate their existing user base in favour of a product that could never be quite as good at being Chrome as Chrome was.
Mozilla had a great browser, and a great community. Someone spooked at Chrome's early success and decided that change for change's sake was necessary, and they have resisted every indication that they have made a mistake.
I recommend PaleMoon for a fantastic experience that is the best of what Firefox was in combination with innovation that makes sense and which takes into account its user base. It was originally a patch on an earlier FF ESR, they have since essentially departed from Firefox, though they still borrow some bits when it makes sense to do so. It's what Firefox should have been if they hadn't taken the detour into crazy six years ago.
Mozilla should have worked with noscript dev
They did.
Regarding NoScript - I have tried uMatrix as a replacement and so far I like it better because it is easier to use having a reload button right there in the block popup. The only thing I am missing currently is a password exporter/importer so I can backup my passwords to a camera card. I imagine I will find a password manager that can do that at some point thought, there are plenty of those.
Facts are history now plebs have politics for religion on social media.