#khtml — Public Fediverse posts

@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)

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...

@[email protected]

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...

@[email protected]

My head always comes up with this picture when people talk about #KHTML

@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. 😉

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

@silvereagle

@RudiK

Also...

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

Fertig.

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

@heiseonline

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

@luana Don't know if it's still the case but in the past KDE & WebKit devs seemed not very happy in cooperation.

It's also sad that #KHTML is not maintained anymore.

For FOSS community some still think Google is better than Apple eh?

@canleaf @[email protected] @LilahTovMoon webkit hasn't been the Chrome engine since who knows how long ago. Probably close to 20 years now'

Went like this: #KDE' #Konqueror web and file browser had a quite clean but basic HTML engine #KHTML. Apple wanted an engine for their new #Safari browser and picked KHTML. Mozilla's gecko (not positive was gecko then) was a mess so wasn't used. KHTML was #GPL hurray! Became AppleWebkit. Google picked it for new Chrome. Soon forked wk to #Blink. Power of GPL.

@pgiulan 95% of all the browsers/engines are just #KDE's #KHTML wrapped in a bunch of different trenchcoats 😁
@AAKL

If you really think about it, 98% of browsers nowadays are actually reskinned Konquerer with enhancements, the other 2% is Firefox.

#konqueror #web #tech #kde #khtml #webkit #blink #funfacts

All major browsers rely on a dark secret: the quirks where native code or the UA stylesheet is varied based on which site you're on.

They're a hell to debug if you're ever caught in one, but they make for interesting stories!

Example:
https://neugierig.org/software/chromium/notes/2009/08/mediawiki-workaround.html

Fix for SVN deadlink:
https://static-codereview.wikimedia.org/MediaWiki/53141.html

Source code of doom:
https://github.com/WebKit/WebKit/blob/main/Source/WebCore/page/Quirks.cpp

History:
https://github.com/WebKit/WebKit/commits/main/Source/WebCore/page/Quirks.cpp

#WebHistory #webkit #chromium #KHTML #MediaWiki #webcompat

@[email protected] @[email protected] @[email protected] @[email protected] @[email protected]

In aller Kürze: #KHTML -> #WebKit -> #Blink.

WebKit wurde als Fork von KHTML gestartet.

Blink wurde von WebCore "geforked", einen Bestandteil von WebKit.

Und Blink ist Bestandteil des #Chromium-Projekts.

On the occasion of #WorldWideWebDay, it's worth a mention that #Oslo, #Norway has been instrumental in giving birth to two most influential browser engines - #KHTML and #Presto. And browsers such as #Opera and #Vivaldi.
A building in #Oslo has a great history: an incubator of the #KHTML & #Presto engines. Presto had a massive influence on web standards & KHTML went on to form the basis of #Webkit and #Blink, on which most web browsers are now based, including Vivaldi.
Continue reading ⬇️ 1/2

@keithzg @kpeace @aral I wonder what the #Konqueror / #KHTML developers browsed with as they were building their software, hm?

Little reminder, that @kde ‘s #KHTML made its way through Apple, returned as #WebKit (#webkitgtk2) to the free desktops and still is a free and one of the most portable browser engines working well and serving as an alternative to #Gecko and #Blink.

Just ran it on a #PPC machine from 2004 yesterday.

Sometimes I wish there was a good #Qt frontend to #Gecko (or whatever the most recent iteration of the #Firefox plugin is called). There are multiple ones for #WebKit and its forks (unsurprising, given that WebKit has its roots in #KHTML), but as a matter of principle I would rather prefer to keep using the minority engine, my small contribution to resistance (weak as it may be) to Google's stranglehold of the Internet.

A trip down memory lane:

"Safari Is Released To The World" [2013], Don Melton (https://donmelton.com/2013/01/10/safari-is-released-to-the-world/).

Via HN: https://news.ycombinator.com/item?id=34304520

#Safari #WebKit #KHTML #Konqueror #SteveJobs #MacWorld #Presentation #Rehearsal #KeyNote

@charlietuna @donmelton Fun fact: #Safari is based on #Konqueror (https://en.wikipedia.org/wiki/Konqueror). And to their credit, Apple has given a lot back to the open source community. :)

(At least, #WebKit, the engine that powers Safari, is based on #KHTML, the engine that powers Konqueror. WebKit was then forked to make #Blink, the engine that powers #Chrome and all #Chromium based browsers.)

“Chrome, 10 Years Later”, Evan Martin (https://neugierig.org/software/blog/2022/12/chrome.html).

Via Lobsters: https://lobste.rs/s/x8uv9q/chrome_10_years_later

On HN: https://news.ycombinator.com/item?id=33917157

#Chrome #Browser #Google #Internet #Web #WebBrowser #Reflection #OpenSource #WebKit #KHTML #Blink

@ruari Well I’ve used #KHTML back in the day when it came with #Konqueror ;)

The thing is, I believe in someone forking #Blink when I see it. Until then, I focus on not letting #Gecko die.

@clarjon1 @danarel @switchingsocial

I'd still say three. Blink is nowadays very different from WebKit, you hardly see a common ground anymore.

So you have three. Actually, did you read my linked #browserDiversity article? Because it's exactly about your point, and I agree: https://css-tricks.com/the-ecological-impact-of-browser-diversity/

(Just developing #KHTML seems like a lost ship to me now.)