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. 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 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |