I have never been able to meaningfully notice the supposed gigantic speed difference between chrome and firefox.
#Software lag switch rust Pc#
I started using FF way back when it was called phoenix and handed out FF for many years with every new build and repair and honestly? Its been ages since I saw a PC with FF installed, everyone has switched to Chrome, also see a lot of PaleMoon and IceDragon installs here but FF? I think that ship has done sailed and this change won’t do anything to stop the bleeding. For those that don’t there is community supported releases and the number of extensions is growing every day, not to mention pretty much all the extensions that work on older FF work fine on PM without porting.Īt the end of the day the numbers do not lie and FF has been in a death spiral for several years. Meanwhile you can just waltz across the street to PaleMoon where they have tossed a ton of legacy Mozilla cruft WITHOUT boning the extensions which has made it more responsive, and have reached out to most of the popular extension devs to support PM. Still a damned shame that they gave the bird to their customers for so long that I seriously doubt having a new faster engine is gonna make a lick of difference, from the fugly UI changes against the will of the community to killing off the reasons why anybody used FF all of the diehard FF users I knew moved away ages ago and their latest usage numbers show they were far from being a minority.Īnd count how many of those either say “won’t be ported” or say “functionality limited” and you’ll quickly find there are more that simply do not work or won’t give you the features you used it for in the first place if you stick with FF. Oh well luckily there is still PaleMoon and the devs of the extensions that I love have switched to developing for PM so if Mozilla dies tomorrow I’ll not be affected in the slightest. I have a feeling this is gonna be one of the final nails in the Mozilla coffin as they really have no selling point over other better supported and better advertised browsers anymore. From what I’ve seen there simply is no way for most extensions to ever work with the new FF engine and the whole selling point for FF was extensions allowing you to have your own custom browser. Of course that is the rotting elephant in the room when it comes to FF…the extensions.
#Software lag switch rust plus#
I use Comodo Dragon (webkit) with PaleMoon (gecko) because I preferred having my extensions to adding a bit of speed plus a fugly UI to FF. Yup ton of webkit based as well as gecko based. I want my browser to get out of my way, and gobbling up processor cycles is exactly not that. Chrome’s gotten way too fat over the years, so I’ve resorted to using Edge on my main computer lately – it isn’t perfect, but it it sure is fast, and places very little strain on my machine. I should definitely give Firefox another try – I’ve tried it over the years but it always felt a little sluggish compared to the competition. So, let’s look at how Firefox got fast again and where it’s going to get faster. It doesn’t mean that today’s Firefox is as fast and responsive as it’s going to be. We call this Project Quantum, and the first general release of the reborn Firefox Quantum comes out tomorrow.īut this doesn’t mean that our work is done. Plus, we’ve had a browser performance strike force scouring the codebase for performance issues, both obvious and non-obvious. Over the past seven months, we’ve been rapidly replacing major parts of the engine, introducing Rust and parts of Servo to Firefox. People have noticed that Firefox is fast again.
0 kommentar(er)
