3 ms·
Well a large part of the problem with a fork is that you don't see a lot of random drive by contributions. As a possible contributor myself a couple times, fire
by StillBored 5y ago
Well a large part of the problem with a fork is that you don't see a lot of random drive by contributions. As a possible contributor myself a couple times, firefox is a development nightmare because it doesn't have a good autoconfig system that lets one download the code and start being productive quickly.
Then like chrome, i'm betting most people can't actually built it in reasonable time on their laptops since it burns a good 64 core machine with 128G of ram for a hour or two. Screw up said configuration, and your in for another rebuild loop. It can take days just to get a working development environment.
- freeopinion 5y agoAnd these are what is holding Firefox back?
- StillBored 5y agoNo, that is one the problems you have to solve before you can have a successful fork unless you happen to have a few million a year coming in to compete with the main branch. I've been known to waste a weekend or two a year working on open source projects. These though generally are small things that scratch and itch for fix a bug. I don't work on projects where it takes a month+ of weekends just to get a working dev environment. I don't think that's unusual, you have to pay people to put up with that kind of pain.