Technology
This is the official technology community of Lemmy.ml for all news related to creation and use of technology, and to facilitate civil, meaningful discussion around it.
Ask in DM before posting product reviews or ads. All such posts otherwise are subject to removal.
Rules:
1: All Lemmy rules apply
2: Do not post low effort posts
3: NEVER post naziped*gore stuff
4: Always post article URLs or their archived version URLs as sources, NOT screenshots. Help the blind users.
5: personal rants of Big Tech CEOs like Elon Musk are unwelcome (does not include posts about their companies affecting wide range of people)
6: no advertisement posts unless verified as legitimate and non-exploitative/non-consumerist
7: crypto related posts, unless essential, are disallowed
view the rest of the comments
I don't keep a log of websites that don't work on FF. The last one I came across is joyn.de, a TV streaming site. They don't tell you that it isn't working on FF, it just crashes when trying to play a video.
For simple stuff not supporting FF is really asinine, but for deeper stuff, like hardware accellerated video streaming, it's not quite as easy. Especially if you are, for some reason, stuck with old frameworks or in-house developed stuff.
Actually, the application that I work on (b2b software) frequently has FF-only bugs, because the frontenders in my team refuse to test every commit on FF. It's just me finding the bugs randomly.
The thing with free and open source is that it's not free to develop. Mozilla still needs to pay the development. Even though the source is open, 99% of the development is done by full-time (and obviously paid) Mozilla employees. Being open source doesn't really help Mozilla bring down the development costs at all.
And that's the second major point where Mozilla is in trouble: They don't really have any sustainable income.