this post was submitted on 08 Aug 2024
1308 points (96.2% liked)

memes

10714 readers
1883 users here now

Community rules

1. Be civilNo trolling, bigotry or other insulting / annoying behaviour

2. No politicsThis is non-politics community. For political memes please go to [email protected]

3. No recent repostsCheck for reposts when posting a meme, you can only repost after 1 month

4. No botsNo bots without the express approval of the mods or the admins

5. No Spam/AdsNo advertisements or spam. This is an instance rule and the only way to live.

Sister communities

founded 2 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 8 points 4 months ago* (last edited 4 months ago)

That's a valid question. Unfortunately, it's difficult to quantify.

The state of browsers in general has been a moving target since NCSA Mosiac; about around 1993 or so. So the last three decades has been a ceaseless grind of new features, security enhancements, performance enhancements, and so on. And this feature set is absolutely monstrous in scale, as it includes backwards compatibility to most of those features (if not all of) back to that beginning over 30 years ago. So, work on any browser is by definition perennial, and it only ever gets more complex.

For Firefox, well, just take a look at their bug tracker. It's broken down by component, but each link on this page is its own fresh hell of things to do, many of which are barely a year old: https://bugzilla.mozilla.org/describecomponents.cgi?product=Firefox

I would also argue that the only other software projects that compare to a web browser in terms of sheer scale, compatibility, and longevity, are things like the Linux Kernel or maybe the entire Microsoft Office suite. IMO, software in this class is a lot of work to keep going, no matter how you slice it.