techhub.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A hub primarily for passionate technologists, but everyone is welcome

Administered by:

Server stats:

4.9K
active users

#khtml

0 posts0 participants0 posts today

@thefish@mastodon.social

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@social.heise.de

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
en.wikipedia.org/wiki/Browser_
#FLOSS #MPL #GPL #FreeSoftware

en.wikipedia.orgBrowser engine - Wikipedia
Replied in thread

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

Replied in thread

@governa

I wish they would just abandon #Blink, as it's clearly #evil.

You've got #WebKit, #Gecko, heck, if I was depending on #Google code, I'd be even giving #KHTML and #NetSurf a serious look.

Companies with the slightest hint of having a soul, please repeat after me:
Google can not be trusted.
Google can not be trusted.
Google can not be trusted.
Google can not be trusted.
Google can not be trusted.
Google can not be trusted.
Google can not be trusted.
Google can not be trusted.
Google can not be trusted.
Google can not be trusted.
Google can not be trusted.
Google can not be trusted.
Google can not be trusted.
Google can not be trusted.
Google can not be trusted.
Google can not be trusted.

Three days ago, the 4th of November, would've been #KHTML 25 year anniversary. 🥳

Hoorrray!

WTF is KHTML?

Chances are you are kind of using it, because #WebKit and #Blink rendering engines are all forked from this open-source project originally intented for the browser of the KDE window environment.

That basically makes #Opera, #Safari, #Chrome, #Chromium and #Brave (and possibly others) all *siblings*.

KHTML is *literally* the mother of all browsers.

"KHTML is dead - long live KHTML!" 😀

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:
neugierig.org/software/chromiu

Fix for SVN deadlink:
static-codereview.wikimedia.or

Source code of doom:
github.com/WebKit/WebKit/blob/

History:
github.com/WebKit/WebKit/commi

neugierig.orgChromium Notes: MediaWiki workaround
Replied in thread

@funbaker@chaos.social

Ich erinnere mich dunkel, daß Alphabet/Google seinerzeit den Part "entschlackt" hat... (bzw. Berichte darüber gelesen zu haben).

https://de.wikipedia.org/wiki/Blink_(Software)
https://en.wikipedia.org/wiki/Blink_(browser_engine)

#Blink is a fork of the #WebCore component of #WebKit, which was originally a fork of the #KHTML and KJS libraries from #KDE. It is used in #Chrome starting at version 28, Microsoft #Edge starting at version 79, #Opera since version 15, #Vivaldi, #Brave, Amazon #Silk and other #Chromium-based browsers and frameworks. (Quelle: Englische #Wikipedia).

@digitalcourage@digitalcourage.social @mozilla@mozilla.social @PuschyMTB@federation.network @michfrankenpt@tube.tchncs.de

de.wikipedia.orgBlink (Software) – Wikipedia

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

Replied to Mark Gardner
@mjgardner @kpeace @aral I was imagining something a bit different but not wholly dissimilar, where the devs only had easy access to text browsers on their preferred and/or personal systems but, having seen GUI browsers in Mosaics lineage on other platforms, were inspired to pursue creating (or joining in the effort and bringing to fruition) one themselves. But I'm sure there were GUI browsers inspired or directly derived from Mosaic available on Linux at the time, I just don't know what they were. I do vaguely remember some #Netscape versions being ported over in the late 90s?

#Konqueror was probably even inspired in some ways by Internet Explorer to be entirely honest — by the time I encountered it in the early 2000s it was already a full browser of both the web *and* of filesystems (both local and network)! Which naturally meant tabbed file browsing and pane-splitting and such, which blew my mind at the time and which most other systems *still* haven't fully caught up with. If you had told me at the time that Microsoft would eventually switch to using #KHTML before they finally added tabs to Windows Explorer I would have laughed at your outlandish science-fiction tale; history takes strange turns.