Skip to main content


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.org/b/yk2n

This entry was edited (2 weeks ago)

reshared this

in reply to jwz

Meanwhile the AI companies are burning the planet to build browsers from scratch as a benchmark.
cursor.com/blog/scaling-agents

This is how we all lose.

in reply to jwz

My read is that Google—Mozilla's main funding source these days—have *ordered* them to spend money on AI (meanwhile supplying the money to do so). No mainstream browser may remain uncompromised by the grift. amirite?
in reply to Charlie Stross

@cstross well, in Google's case the pressure is most likely internal. For Mozilla it'd be interesting to see if there was a gentle push from the outside or if this is inbred^W in-board general idiocy.
in reply to Oblomov

@oblomov @cstross 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?

in reply to Jens Finkhäuser

Mozillans didn't like it, but Mozilla also considered a unified web more important than open standards, where the definition of "open" includes practically open to implementors.

So fuck you very much for two decades running, Mozilla.

This entry was edited (2 weeks ago)
in reply to Jens Finkhäuser

@jens @cstross
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.
in reply to Oblomov

@jens @cstross
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-/).

in reply to Oblomov

@oblomov @cstross Yes, the WGs were running in parallel for a while. Of course, you don't come up with something like that in a few days. But chrome I'm fairly sure was a thing already.
in reply to Jens Finkhäuser

@jens @cstross IIRC the WHATWG was created in 2004, but Chrome is from 2008. I think Google might have been putting pressure on Mozilla & Opera to push for the whole “web app” angle because of their forays into Gmail and Maps that started around that time. When Chrome was first released the WHATWG and the W3C had already been armwrestling on «who gets to decide what HTML is» for one or two years, and with Chrome entering the fray the W3C basically gave up.
in reply to Oblomov

@oblomov @cstross Indeed. w3.org/standards/history/xhtml…
in reply to Jens Finkhäuser

@oblomov @cstross WHATWG started in 2004, with Mozilla, Google, Apple and Microsoft.

Apple forked KHTML into WebKit in 2005.

in reply to Jens Finkhäuser

@oblomov @cstross The line is straight when you know the route it took, seemingly coincidental otherwise.

But as the HipCrime Vocab defines "coincidence": you weren't paying attention to the other half of what was going on.

And, err, though I'm in danger of exhausting my quote quota, the proof is in the proverbial pudding.

in reply to Jens Finkhäuser

@oblomov @cstross As you will note by some research, in April 2005, so before the publication of WebKit, there was already discontent in the KHTML community in how Apple was developing WebKit as a fork.

How can that be? They complied with the letter, but not the spirit of the GPL. web.archive.org/web/2005042823…

in reply to Jens Finkhäuser

@jens @cstross yeah, this is also something I tried pointing out on the subsequent rapid expansion of Chrome. Everybody was saying «relax, (the core) is free software». Which matters very little when the only thing that truly matters is who controls the platform. FLOSS is not immune to the dangers of monocultures (or of corporate control for that matter).
in reply to Jens Finkhäuser

@oblomov @cstross @lisamelton At any rate, Dave Hyatt was a former Mozilla dev who switched to Apple and started Safari, and so this entire thing.

He was also representing Apple at WHATWG from what I understand.

in reply to Jens Finkhäuser

@oblomov @cstross @lisamelton And then we know how much Google pays Apple yearly since, well... neither 2004, the WHATWG start, nor 2008, the Chrome start, but... did you guess when?

2005.

businessinsider.com/google-app…

It's all coincidence until it isn't.

Google's enclosure of the web has over two decades of history, back when their motto was still "Don't be Evil".

in reply to Jens Finkhäuser

@oblomov @cstross The WHATWG position paper is from 2004: w3.org/2004/04/webapps-cdf-ws/…

The working draft cited there edited by Google. Full authors at the bottom:
whatwg.org/specs/web-forms/cur…

XHTML 2.0 specs have been sitting in decision limbo since 2002, when it was finished: w3.org/2007/03/XHTML2-WG-chart…

in reply to Jens Finkhäuser

@oblomov @cstross The last bit of glue, which I can only give you second hand from personal acquaintances I shall not out here, is the frustration in XHTML WG about Google and Apple blocking adoption with ever more spurious reasons.

There's probably an archive of minutes somewhere.

in reply to Jens Finkhäuser

@oblomov @cstross I mean, there's also that Mozilla Corporation was launched in 2005, and crypto turd Marc Andreessen decided that was a good moment to heap praise on the new CEO content.time.com/time/specials…

Tumultous times, which weren't all dark. Firefox started making waves after this.

So here's another thing to contemplate.

in reply to Jens Finkhäuser

@oblomov @cstross Consider as well that after this it's only three years that Jonathan Zittrain wrote "The Future of the Internet", which you should read if you haven't.

futureoftheinternet.org/

The central theme is contrasting "generative systems" to "tethered appliances".

The first describes incomplete things with an unspecific purpose, such as the PC, early Internet or Web.

The second describes single purpose things tethered to this one function, and a corporate support infrastructure

in reply to Jens Finkhäuser

@oblomov @cstross The point of this comparison is in the book's tagline "and how to stop it".

It took three years of Safari to recognize and document the direction of the web as part of a larger, repeating trend. Apologies to @pluralistic , but "enshittification" is in a sense "just" a much-needed focal point for the same pattern.

Yes, that book launched the same year as Chrome. Prescient? Or pattern recognition.

in reply to Jens Finkhäuser

@oblomov @cstross If you're up for it, also read Ben Tarnoff's Internet for the People.

versobooks.com/products/2674-i…

It reads like an almost straight up sequel to Zittrain, except the future that could've been prevented wasn't. So now the focus is on damage control.

Published 2022, 15 years later.

The history of how today's Web developed is traceable, and the patterns of how things coincide and work out can be recognized and traced.

in reply to Jens Finkhäuser

@oblomov @cstross Just to connect some more personal anecdotes here. I joined a video startup in 2006, quality-wise leagues ahead of YouTube. Folded, TL;DR, in 2008.

Anything I do related to @interpeer started then. I had enough reasons to not *do* much about it until the 2020s. But I can also draw a line in how my reasoning evolved all the way back to those years, and before, and so forth.

I cannot begin to describe the mixture of emotions I feel about not starting sooner.

in reply to Jens Finkhäuser

@jens I hired David Hyatt onto the Safari team. He did not start the project. I did, at the behest of Scott Forstall.

Dave didn't join the project until about 9 months after work began. He was quite dubious about KHTML and KJS in the beginning, but he learned to love them.

BTW, I lured Dave to join by "accidentally" letting him know that Marklar (our Intel port) really existed. 😂

@oblomov @cstross @jwz

in reply to Lisa Melton

@lisamelton Ooh, that is new to me indeed!

It's kind of hard to piece things together from public announcements. Apologies if I get these things wrong!

@oblomov @cstross @jwz

in reply to Jens Finkhäuser

@jens That is incorrect. We forked KHTML and KJS in 2001 shortly after I arrived at Apple. We didn't make it known that we had forked it until Safari was released publicly as a beta in early 2003. After that we released periodic tarballs of our changes. Internally we had called them WebCore and JavaScriptCore and referred to both as WebKit. I'm the person who christened it as such. 2005 is when we put WebKit on a public repository and invited participation.

@oblomov @cstross @jwz

in reply to Lisa Melton

@lisamelton Yes, I gave some evidence of that later - but your version is, obviously, way more precise! @oblomov @cstross @jwz
in reply to jwz

according to Mozilla they will spend $130 million on AI bullshit. The $1.4 billion number is their total reserves.

stateof.mozilla.org/ledger/

in reply to jwz

I feel like you could fix a lot of browser bugs with $1.4 billion (assuming it isn't wasted on Clod subscriptions for the sloperators).
This entry was edited (2 weeks ago)
in reply to jwz

So... I assume people have already researched alternative browsers.

Any recommendations.

in reply to jwz

jfc. and they are putting not one cent of that to FLOSS projects, right?
in reply to jwz

FF used to be OK but sadly enshitified now. Not as bad as Chrome or Edge. Yet.
in reply to jwz

1.4 BILLION after they closed their Open Source sponsorships too... 🙄
in reply to jwz

Did mozilla somehow end up with all the AI bros not competent enough to grift from VCs rather than nonprofits or something?
in reply to 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.

in reply to jwz

out of curiosity, what is a good, trustworthy, no nonsense upstart web browser these days?
in reply to jwz

that's like 10-15 F-35 fighter jets, or 1/20th of one block of a nuclear powerplant
in reply to jwz

As much as I dislike the Chromium hegemony, I've since switched to Vivaldi because of Mozilla's tone deaf approach to enabling this AI shit storm bubble.

There are some amazing Firefox forks, but how much hope can we really have for them if Mozilla is handling their financial setup this poorly?

in reply to jwz

Jesus. Makes me feel better about moving to Waterfox/Librewolf, as they at least strip out the crap Mozilla throws in. Upstream is still always a worry, but at least there's an emergency hatch for the moment.
in reply to jwz

said it for year.

they trow money in AI, yet help of the security people i know won't use anything related to firefox, due to a lack of sandbox security, and of course of the chromisation of firefox (why use a cheap copy when you can use the original).

in reply to jwz

That's about 1000 person years of development. So you could get a team of say, 10 people working full time for 100 years, or you could increase the team size up to 100 people working full time for 10 years. That's a lot of actual Firefox development they are throwing away.
in reply to jwz

I honestly thought you might have been exaggerating, but then I clicked through to the article...and jesus effing christ, the whole board need to be launched into the sun.
in reply to jwz

They are not spending 1.4 billion on AI. This would be silly to spend all their money. But they will spend 20% of their annual budget on AI, roughly $120M. Still a lot of money.
in reply to jwz

Their money comes from Google. They do what Alphabet tell them to do. This is the elephant in the room with Mozilla.
in reply to jwz

I would have been shocked if it went any other way at this point.
in reply to jwz

@mozilla #WTF are you doing? No one wants you to do AI. DO something useful!
in reply to jwz

Maybe I will sound like Cato " Carthago delenda est" to say it over and over again, but for now Mozilla has last independent browser engine. I know about Google donations for it, but still until new engine is not ready we have only Mozilla with all Headquarter stupidity.
in reply to jwz

That's it, I'm backing up my bookmarks and changing browsers, I'm not even anti-AI, but this is just ridiculous, nobody is asking for this.
in reply to jwz

Well, the good thing is I had a great reason to stop donating to Mozilla.
in reply to jwz

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. mastodon.social/@jwz/111546146…
in reply to jwz

Why is this tagged brand necrophilia?

Weird ass stuff man

in reply to jwz

imagine a lot of useful stuff that could be done with that
in reply to jwz

that’s why their CEO is worth so much: Brilliant business leadership!