Right now is the best period of time yet for Firefox-based browser, especially when most alternative browsers are Chrome-based.
While there are a bunch of forks like Librewolf and Palemoon, they provide features mainly for power users like hardened privacy and tweaked user-prefs. A year ago the only fork I knew of, based on recent stable versions of Firefox and added productivity features on top was Floorp. I was very surprised at the hype and sudden popularity of Zen Browser in the past few months and have been curious why it grew so much faster than Floorp which has been around for much longer, look at the Github star graph: https://star-history.com/#zen-browser/desktop&Date. Zen Browser currently has 19.3K stars while Floorp has 6.1K.
Reasons I can think of are the following: heavy promotion of the browser by the devs and community on places like Reddit along with emphasizing its ‘zen’ philosophy, really fast development (it now has way more features than Floorp), and the Zen mods store, where you can install CSS mods.
What are your thoughts and reasons for Zen Browser becoming so popular so fast? (while its not mainstream, it did grow fast in among Firefox and power users)
I’ll start believing or caring about any alternative browsers when I see a big influx of money comming to a browser project. Just grabbing a codebase and changing some settings and releasing it with a new name is not really creating or maintaining a browser. People keep thinking that it’s easy to maintain a huge project like a browser by just praying and volunteers.
Money isn’t important. Some complex software is, in fact, maintained by unpaid volunteers who feel strongly about the project. That doesn’t mean it’s easy (in fact it’s quite difficult to keep the lights on and the code up-to-date), but it is A Thing That Happens despite being difficult.
What is important is the size of the codebase (in the case of a fork, that’s the code either written for the fork or code that the fork preserves and maintains that isn’t in the original anymore), the length of time it’s been actively worked on, and the bus factor. Some would-be browser forks are indeed trivial and ephemeral one-man shows. Others have years of active commit history, carry tens or even hundreds of thousands of lines of novel or preserved code, and have many people working on them.