Edit: Oops, didn't see the "open source" clause. So Trident, EdgeHTML, and Presto don't count.
All of that being said, it all depends on your expectations. You can totally make a browser that is capable of going to web forums and posting on Hacker News, browsing the SerenityOS website and maybe even Wikipedia for instance. If you want to build something that supports pre-2005 HTML/JS, that's probably quite feasible.
Do you think you could build this in 2 years? The answer is yes, you could.
Again, this isn't to minimize the accomplishment, this is great, it's just to say, while building a hobbyist browser must be fun for sure, and I'm sure this browser can be useful to browse many websites out there, particularly if said websites intentionally restrict which HTML features they use. However, it's probably not realistic to think you could compete with the commercial browsers. They have dozens of people who have been working full-time on those projects for two decades and they are constantly adding new features.
I think if Andreas Kling was here, he would probably agree. I'm sure his goal was never to replace Chrome/Firefox or compete with them, but rather to learn, educate, and have fun. I congratulate him on his success and for reaching the milestone of being able to sustain himself from his passion project.
I'm on mobile or I'd go find a source, but I'm fairly certain some key people left before all that went down.
Not that maintaining a web browser is easy, but they WERE doing it, to varying success.
I'm worried about that as well, but it's not really fair to attribute blame to most people at Opera, especially prior to the China thing. Things were okay there for a long time before that.
No, it's not.
> if Mozilla ever tanks, we could have a complete WebKit browser monoculture
Not a risk. Chrome dominates, and it uses Blink, not WebKit. (Yes, the distinction matters, and no, it is not a distinction that is minor/negligible/insubstantial.)
Does that really matter much, if it's open source? A lot of software converges on one or a few standard libraries or applications.
There is another cost that people don't talk about as much, and that is the cost to understand a large, alien codebase enough to be able to understand and change it. If the effort to contribute is too high, you can't get a second group of programmers to rally around the fork, and the new project will fizzle.
As an example, Google understands the economics of code very well. They know that there is little threat to market dominance for them to release Android or Chromium as open source.
There is no rule that says a "browser" must match Google's in-house Chrome or its outsourced Firefox (all salaries of Firefox developers are currently paid with money from a deal with Google).
Look at how many browsers exist already for Gemini. How many were funded by advertising. Probably zero. The multi-million dollar corporations have a vested interest in keeping the notion of "browser" so complex that independent authors cannot even contemplate it.
[0] https://blog.samuelmaddock.com/posts/google-widevine-blocked...