Show threadR.L. Dane    🍵 Apr 13

@moses_izumi

I never use it because I don't know how well maintained the codebase is, and unfortunately, in 2026, a web browser isn't something you just use willy-nilly. The web is a ruddy minefield.

I don't know if it's even #KHTML-based anymore, or just yet another wrapper around QtWeb (probably not remembering the name right) a.k.a. Blink.

Having the file manager and web browser be the same thing is a very early 2000s idea ;) (think earlyish versions of Internet Explorer)

teveFeb 16
Our team got a new members, I was just telling to them that I used to run #kde desktop on P2 400Mhz with 128MB of memory and recompiled #khtml daily on the background. I had a bunch of terminals, mail client and web browser running but I realized that I do use exact same apps today, just need 64x more memory...
KDE PlasmaJul 27, 2025

I gotta say, out of all good things KDE has done to the world, KHTML is not one of them. Thanks to that we now have Safari and Chrome which both suck.


#kde #khtml #netscape-4-ever
Nordnick 🌐May 4, 2025

@thefish

Der Haken ist die "Render Engine", der Teil, der #HTML/#CSS zur Anzeige bringt. Dazu kommt noch #JavaScript.

#Presto war eine europäische Engine (im originalen #Opera).

#Gecko steckt in #Firefox und geht historisch auf #Netscape zurück.

Und dann gab es #KHTML (aus dem #KDE-Projekt, wenn ich das richtig erinnere). Davon wurde #WebKit abgeleitet (was heute von #Apple genutzt wird). Davon wiederum wurde #Blink abgeleitet (von #Google).

Und das war's auch schon mit den aktuell verbreiteten "Render Engines". Je nach Zählung also nur zwei bis drei. Extremst übersichtlich. Und trotz "Open Source" eben in der Hand von wenigen... noch dazu US-Entitäten.

Damit stehen und fallen alle Browser mit der Entwicklung der "Render Engine", auf der sie basieren...

@heiseonline

MJ Apr 30, 2025
My head always comes up with this picture when people talk about #KHTML
Show thread𝓒𝓱𝓻𝓲𝓼𝓽𝓸𝓯 𝓓𝓸𝓷𝓪𝓽Mar 8, 2025

@kubikpixel

#chrome #firefox #web #browser #joke #webbrowser #privacy #internet #it #fun

Actually all of them (except Firefox, of course) are based on #KHTML, which is, what Apple forked for #WebKit, which Google forked for Chrome. 😉

Show threadElias ProbstJan 27, 2025

@j3j5 if you dig deeper, it's all just #KDE's #KHTML deep below the surface... (except of Firefox) 😄

@silvereagle

Nordnick Nov 30, 2024

@RudiK

Also...

* #Gecko
* #KHTML -> #WebKit -> #Blink

Fertig.

Oder fehlt ein verbreiteter und aktiv entwickelter #HTML-Renderer?

@heiseonline

rivalSep 27, 2024
Some #history, like #Android with #GNU+#Linux...
«#Microsoft's new, #Chromium-based #Edge, was remade with the Blink #engine. #Google originally used #WebKit for its #Chrome browser but eventually forked it to create the #Blink engine. #Apple created the WebKit engine for its #Safari #browser by #forking the #KHTML engine of the #KDE project.»
«#Mozilla develops the #Gecko engine for its #Firefox browser and the #Thunderbird #email #client.»
https://en.wikipedia.org/wiki/Browser_engine
#FLOSS #MPL #GPL #FreeSoftware
Browser engine - Wikipedia

Show threadD1re_W0lfSep 18, 2024

@tchambers @Vivaldi True.

Curious about #servo but I’m not getting my hopes high.

Perhaps the same way #webkit started as a fork of #KHTML and later Google forked it, maybe we need to go two steps back and a fresh restart somehow.
Again, not getting my hopes high.