Modern Reddit is one such bloated mess that I was talking about. Even Pale Moon, being a much newer form of “classic” Firefox than the ones you cited, chokes when you load long Reddit threads with it (although to be fair, the type of hardware you run it on also plays a vital role here). The website the browser has to load has a larger impact on the perceived performance than anything the browser itself does. I think none of the older Firefox versions would still be quick today if they were confronted with today’s JavaScript-heavy bloated websites. After jumping ship from Firefox, I first went with Ungoogled Chromium and later with Brave. Some other incidents like Cliqz experiment, Mr Robot extension, ever new invasive telemetry and other FF experiments, lousy privacy defaults seldom improving, and other aspects didn’t help, either. Mozilla killed off those extensions, and I stopped using Firefox as my primary browser.
#FIREFOX 45.0 KEEPS CRASHING UPDATE#
No idea what the issues are, but any of the above (or a combination of them) could realistically be have been a FF user for many years, I came to like it in the past for the user-friendliness customizing it, but since perhaps around after FF 35 or so it started to go downhill by bloating and increasing it’s attack vector surface (as most browsers actually) etc so I quite recently tried what is supposed to be perhaps some of the “best” versions of Chromium based browsers, namely Brave, but it has been a buggy path, too many extensions have issues, and when using the Tor mode it disables all extensions of which some are really crucial in keeping the browser safe and somewhat private, I don’t know what is better but Brave is so far not the answer either.Īnyhow, I updated only very recently after having used a couple of years old FF version to 83 and now just updated to 84, and I must say latest FF feels quite nimble and solid, and certainly doesn’t pale in comparison to Brave in any way although it requires lots if tweaks, but none of these “modern” browsers are as quick as the very old FF versions such as 17 ESR, 24 ESR, they were and still are speed-monster in comparison, I just some times wish someone could take the code from 17 ESR and add latest cryptology to TLS 1.3 and update other things like JS engine etc.Īnd then we have Palemoon, probably the most sane choice although even I barely use it but perhaps should, it simply works and is fast enough, but I guess IH hates PM simply because of personal issues with the PM team? was actually a Firefox user until 2017 (before their migration to WebExtensions), because powerful extensions like Tab Mix Plus which really made my life easier made me stay with it.
– Not getting as much outside contributions compared as e.g. – The hard deadlines on a 4 weeks release schedule(!) being too inflexible. – Them trying to cram too many features into new milestones. – Relying too heavily on telemetry – telemetry sometimes doesn’t cover the wider scope of why e.g. – Inadequate quality assurance, relying too heavily on machine testing. We could theorize on why their releases tend to have beta quality these days, some causes could be: Mozilla is fully in control of the development effort including engine development, they have no excuses.
Because Vivaldi adds rather major modifications to Chromium compared to Chrome, Edge, Brave etc., it is more prone to breakage, as a result of them having to use Google’s code while also wanting to maintain their ambitious UI effort. Vivaldi’s UI is a special layer on top of Chromium which seems to break with every single new major release of Chromium, and they have to fix the breakage causes in time as to not fall behind. It can still happen occasionally, but with Mozilla, it happens all the time.Ĭompare this to how Chromium is being released: Major release, later 1 – 2 security updates for that major release, then next major release. Why? Because you can expect an emergency fix within days after each major release… Emergency fixes are only rolled out when a problem is both obvious and fairly widespread, and such problems are usually caught in the beta phase. Think the way Mozilla manages releases is indeed indicative of my “their stable is actually their beta” theory.
0 kommentar(er)
