douglasg14b

@douglasg14b@lemmy.world

• ⁨Comment⁩ on ⁨Firefox has an ambitious new roadmap, the browser is also losing millions of users a month⁩ ⁨⁨5⁩ ⁨days⁩ ago⁩:

  I hope you know that Waterfox and LibreWolf have their fate tied to Firefox, right?

  These aren’t hard forks. They consume the engineering efforts of Firefox itself in order to stay relevant. They aren’t developing their own solutions to web standards and CVE patches, except in extreme circumstances.

  If Mozilla loses funding for their engineering organization, which is the grand majority of their entire budget, Firefox stops keeping up to date with web standards and security patches and rapidly falls behind. Leaving just Chrome as the only option, or Safari, but I know none of us want to choose Safari.

  All the soft forks go with it.

  ---

  Now, if all the soft forks abandoned their own projects in order to pool their efforts together to maintain a single fork in this scenario, then they might make some success in staving off irrelevancy, which, instead of becoming irrelevant in the course of a couple of years, might take half a decade instead. Which does leave enough time to cobble together enough contributors and a large enough project to keep it afloat.

  But I highly doubt that all these various forks will pool their engineering efforts into a single project, at least not immediately and at least not willingly.

• ⁨Comment⁩ on ⁨Firefox has an ambitious new roadmap, the browser is also losing millions of users a month⁩ ⁨⁨5⁩ ⁨days⁩ ago⁩:

  This is a broad misunderstanding I keep seeing here on Lemmy.

  These forks rely heavily on Firefox core engineering and development, which, if Firefox dies off, they will no longer have access to, thus relegating them to history as well.

  These are not hard forks. These are forks that maintain release parity with Firefox itself, absorbing the grand majority of all engineering efforts into Firefox into their own projects, meaning they are strongly tied to Firefox’s success or demise. And “strongly” is an understatement. We’re talking 95 to 99% of Firefox engineering efforts are consumed by these forks.

  So somewhere from 1 to 5% of the engineering effort these forks rely on to continue to stay relevant, secure, performant, and up to modern web standards is provided by their contributors.

  Keeping Firefox up-to-date with web standards and security is an engineering nightmare. I mean, just look at Safari.

  Having forks is awesome, but putting blinders on and sticking your head in the sand, believing that these forks are independent browser developments is absurd.

• ⁨Comment⁩ on ⁨Funded in 5 minutes - the open source modular mini computer 'Pilet' is on Kickstarter⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  God, lemmy.world needs to get rid of this guy…

  Toxic all around

• ⁨Comment⁩ on ⁨Court rules Gabe Newell must appear in person to testify in Steam anti-trust lawsuit⁩ ⁨⁨2⁩ ⁨years⁩ ago⁩:

  ITT: A lot of corporate simping