6 ms·
Don’t forget where Chromium came from. KHTML lead to Safari lead to Chrome which lead to Chromium. It’s been forked and obounced from open source to corporation
by zeckalpha 8y ago
Don’t forget where Chromium came from. KHTML lead to Safari lead to Chrome which lead to Chromium. It’s been forked and obounced from open source to corporation to corporation to open source.
- zitterbewegung 8y agoAlso to note on the engines used it went from khtml to WebKit and then google forked WebKit into Blink. Also opera switched from writing their own engine and moved to chromium .And now it seems the next version of edge will also use Blink being derived from chromium. Which puts everyone in a position that on all platforms you are using WebKit derived browsers (also mobile is in the same boat with WebKit powering both Chrome and Safari.
- ajross 8y agoAll thanks to the LGPLv2, I guess? Maybe we should have handed the internet over to RMS.
- utopcell 8y agoThat'd be a nightmare.
- snaky 8y agoAds would be not as perfectly targeted as they are now?
- heavyset_go 8y agoThe horror!
- utopcell 8y agoThey probably would, they'd just be named GNU / Ads.
- femiagbabiaka 8y agobeing sincere, not flaming. why a nightmare?
- magicalist 8y ago> All thanks to the LGPLv2, I guess? No, mostly BSD.
- cat199 8y agoWell.. I guess we should have handed over the internet to BSD UNIX then. sounds pretty good actually.
- tracker1 8y agoI don't have them memorized, but looks like a BSD License variant at first glance... https://chromium.googlesource.com/chromium/blink/+/master/LICENSE https://chromium.googlesource.com/chromium/blink/+/master/LI...
- ajross 8y agoThe original KHTML base that was picked up by Apple and turned into WebKit was LGPLv2, which is why source was ever available at all. Other stuff has surely been added under other licenses, and I've certainly not audited it. But I'm sure the copyleft portions are still in there.
- arthurcolle 8y agoSafari led to Chrome? Really? Source?
- hugs 8y agoThe Google Chrome Comic, page 12. "WebKit is the open source rendering engine we used for Google Chrome" https://www.google.com/googlebooks/chrome/small_12.html https://www.google.com/googlebooks/chrome/small_12.html (WebKit is the rendering engine that powers Safari.)
- arthurcolle 8y agoReally cool comic! Thanks for sharing it. Very useful dive into some details I've managed to not know about until this present moment. Any other internal tooling/stack related comics for useful Google products that are worth mentioning in your opinion?
- AlotOfReading 8y agoApple ported KHTML to Mac OS, calling it Webkit. It was released as part of the initial Safari release in 2003. They had a breakup with KHTML a few years later and open sourced Webkit separately. Webkit then became the basis for Chrome when it was launched by Google, until they forked in turn and made Blink.
- mda 8y agoA browser has many other parts than rendering engine. So it is not fair to say Chrome is derived from webkit or safari. You can say chrome rendering engine was initially based on webkit which was based on khtml. And today that shared parts are quite small in the general picture.
- heavyset_go 8y agoKHMTL was the basis for WebKit in Safari, and WebKit is the rendering engine Chrome uses.
- 8y ago
- mda 8y agoSure they allstand on the shoulders of giants, however you are mixing technologies a little bit. A browser is a lot more than an html engine, there is almost nothing left from khtml in either Chrone or Safari.