#WEBKIT VS BLINK CODE#
#WEBKIT VS BLINK PC#

Sidenote: I wanted to follow the Webkit source through Webkit, for example git log -follow.

#WEBKIT VS BLINK CODE#

Webkit is just a kit/library, and whilst the smallest code base, there a lotīlink’s source esp when you take in consideration gclient et al isĮxpansive and firmly under the grip of Google. Runtime (V8?) is not in the Blink git repo. Of sloc in git, but Chromium has more in their source distribution becauseīlink’s git repo is not a “monorepo” like Firefox’s. Firefox has rust / python toolĬhains in the source that bloat it quite a bit. Historically, browsers have relied on vendor prefixes (e.g., -webkit-feature ) to ship experimental features to web developers. Sources… that’s because a release is cut from the git, which isįirefox has the cleanest git to source mapping. Now, edit your post plz to clarify that this is an unconfirmed rumor. An unconfirmed rumor from a questionable source, which could very well be wrong. Not big news at all Since this is a rumor. WebkitĤ0M doesn’t come close to the 5-3M of code I got from the Which forked into Webkit, which forked into Blink/Chromium.

I suspect the git - mercurial bridge is problematic. The total is ~130M, but when I look at just the firefox-78.0.1 sourceĭistribution… it’s just 43M or if you just want to look at source files withĬloc … 23M. I’m not quite sure why there are horizontal lines. However if you look at cloc’s analysis of 49M… it’s pretty close to 45M! Gecko Dependencies (look at Arch’s PKGBUILD for some clues).Tests, I made a testbloat.sh script to rip them out.There are too thorny issues whilst counting to be aware of before we get started: Don’t worry, I’ve been guilty of this too, though I’m trying to change.Ĭode, there is more complexity. You can moan about the Web all day, but if you are not looking at the codebase, then you’re just a consumer and you’re not really helping. Given its track record there, it makes sense for the company to take control of its own rendering engine.Since my video on measuring the SLOC using

It's done an excellent job of the V8 JavaScript engine, creating a fast, capable engine. Google, it seems, is also very good at optimizing code when it comes to browsers. And while having all that dead wood buried in the codebase might be fine on desktop and notebook systems with a beefy processor and bags of RAM, on mobile systems with limited processing power, storage, RAM and power, a more focused, streamlined rendering engine would be better for all. There's no doubt that Apple has effectively managed the project and transformed it into a capable post-PC era rendering engine, but it is clear that if Google can eliminate 4.5 million lines of code from the project, then there's a lot of dead wood in there.

#WEBKIT VS BLINK PC#

WebKit is long in the tooth, and is a product of PC thinking. The reason Google wants Blink is down to one thing - the post-PC era. JAM03/V To prevent wireless camera when you are in hotel,home,office or in. Sure, Google is interested in adding new features, but in such a multi-platform world, the idea of filling Blink with features that are incompatible with other rendering engines is almost unimaginable. Blink cameras, like most wireless technology, are susceptible to hacking. The fact that Google focused on simplifying the WebKit is telling.

Webkit vs blink