←back to thread

Disable AI in Firefox

(flamedfury.com)
197 points speckx | 4 comments | 24 Oct 25 17:11 UTC | HN request time: 0.001s | source
Show context
porphyra ◴[24 Oct 25 17:29 UTC] No.45696986[source]▶
Mozilla could have had the no-nonsense, high performance browser backend that everyone uses to build their own browsers (like the recent glut of AI browsers), instead of everyone using Chromium/Blink. In the past, Gecko was really the go-to choice for this. They almost had a second shot with Servo. But they kinda really dropped the ball on the technical capability of the browser while continuing to be distracted by all sorts of random gimmicks like Pocket and then this. Sad!
replies(6): >>45697043 #>>45697055 #>>45697124 #>>45697237 #>>45697283 #>>45697334 #
dontlaugh ◴[24 Oct 25 18:00 UTC] No.45697334[source]▶
Gecko was always hard to embed, which is why WebKit was developed by Apple and then widespread in open source projects.
replies(1): >>45697440 #
1. mionhe ◴[24 Oct 25 18:10 UTC] No.45697440[source]▶
More accurately, why WebKit was forked from khtml by Apple.
replies(1): >>45697452 #
2. dontlaugh ◴[24 Oct 25 18:12 UTC] No.45697452[source]▶
Sure. KHTML wasn’t embeddable outside KDE either until Apple made that happen.
replies(1): >>45697624 #
3. ASalazarMX ◴[24 Oct 25 18:28 UTC] No.45697624[source]▶
That was always KHTML's goal, but Apple saw value in it for their business plan, just like it saw value in FreeBSD to reuse as their OS's base.
replies(1): >>45700277 #
4. dontlaugh ◴[24 Oct 25 23:54 UTC] No.45700277{3}[source]▶
Sure. I wasn’t trying to say that Apple made WebKit from scratch, merely that they developed it into something easily embeddable. That very much was novel at the time.