Mozilla has 1.4 BILLION dollars that they are spending on some AI bullshit.
Uncategorized
66
Posts
54
Posters
0
Views
-
Mozilla has 1.4 BILLION dollars that they are spending on some AI bullshit.
That's billion with a B. So if you held out hope that filling out surveys or shitposting through it might turn this ship around, no. That much money has an event horizon.
Mozilla is cooked.
@jwz fuckin' magic beans
-
Mozilla has 1.4 BILLION dollars that they are spending on some AI bullshit.
That's billion with a B. So if you held out hope that filling out surveys or shitposting through it might turn this ship around, no. That much money has an event horizon.
Mozilla is cooked.
@jwz "That much money has an event horizon." 🤣
-
-
Mozilla has 1.4 BILLION dollars that they are spending on some AI bullshit.
That's billion with a B. So if you held out hope that filling out surveys or shitposting through it might turn this ship around, no. That much money has an event horizon.
Mozilla is cooked.
I'm old enough to remember when the AI company with $1,400,000,000 in the bank held a bake sale to keep their mail reader running. https://mastodon.social/@jwz/111546146333271392
-
@oblomov @cstross @jwz Consider that Mozilla being cooked has a few decades of history.
Back around 2007ish, I was working with a few folk who either came from or later went to Mozilla. Anyhow, some of them were involved with the XHTML 2.0 spec.
Which was finished.
But then got ditched.
Because Googleites insisted a "living spec" was the right thing, which can only be implemented by whoever throws the most money at it, and we now have HTML5 and a browser engine monopoly.
And Mozilla?
-
Mozilla has 1.4 BILLION dollars that they are spending on some AI bullshit.
That's billion with a B. So if you held out hope that filling out surveys or shitposting through it might turn this ship around, no. That much money has an event horizon.
Mozilla is cooked.
@jwz Why is this tagged brand necrophilia?
Weird ass stuff man
-
@oblomov @cstross @jwz Consider that Mozilla being cooked has a few decades of history.
Back around 2007ish, I was working with a few folk who either came from or later went to Mozilla. Anyhow, some of them were involved with the XHTML 2.0 spec.
Which was finished.
But then got ditched.
Because Googleites insisted a "living spec" was the right thing, which can only be implemented by whoever throws the most money at it, and we now have HTML5 and a browser engine monopoly.
And Mozilla?
-
@jwz It feels like someone needs to pull a Firefox on the Mozilla Foundation like Firefox did on the original Mozilla browser when it had lost its way.
Take the core technology of Firefox & fork a non-AI browser that is focused on the web. That's what a large swath of people want. Then let the downloads do the talking.
Firefox "won" because a lot of people were using it. Web developers loved it.
Make a browser that people fall in love with because it works and is fast & reliable without AI.
-
IIRC the WHATWG was set up before Google had its own browser (I think it was Mozilla + Opera + Apple at the time?) and it almost made sense, although there was no reason to ditch XHTML 2.0 altogether. What really drives me mad is that EVEN IF one could consider the XEvent and XForms interface to be suboptimal for the kind of “dynamic” web that was being pushed (possibly by Google behind the scenes) that was really no reason to throw away the whole of XHTML 2.
-
IIRC the WHATWG was set up before Google had its own browser (I think it was Mozilla + Opera + Apple at the time?) and it almost made sense, although there was no reason to ditch XHTML 2.0 altogether. What really drives me mad is that EVEN IF one could consider the XEvent and XForms interface to be suboptimal for the kind of “dynamic” web that was being pushed (possibly by Google behind the scenes) that was really no reason to throw away the whole of XHTML 2.
There are still so many features that had been introduced there (client-side includes with fallback, “everything is a link”, etc) that are still sorely missing 8-(
I wonder if there was also a growing dislike for XML in general behind this choice? (hurr durr namespace confusing). It's ironic that we have to thank MS for pushing for the little support of XML in browsers we still have (and they are now working on removing 8-/).
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@torgo please come visit at the social web developer room!
-
@torgo me too from London! Eurostar.
-
Europeans for some reason:
❌️ "Digital Sovereignty"
✅️ "Digital Soverinity"
-
Ok we’re doing this! On my way to #FOSDEM! 🚄 I’ll be helping out at the “CRA in Practice” dev room tomorrow and generally nosing around otherwise.
-
-
@Alyssa you're welcome! 🙋🏻♀️
-
titolo: cali canto?
scattata com'è venuta...
🔁 condivisione gradita
30 Gennaio, 2026 11:45
-
Giulio Regeni: riprende il processo
@giornalismo
articolo21.org/2026/01/giulio-…
Con una sentenza depositata oggi, la Corte Costituzionale ha dichiarato l’illegittimità dell’articolo 225, comma 2, del codice di procedura penale per violazione dell’articolo 24 della Costituzione, nella parte in cui non prevede che l’onorario e le spese del
