I find it particularly interesting that alongside Opera’s announcement which ties so heavily into Chromium’s, Mozilla also announced a new project in partnership with Samsung. We want things to keep getting better and better, which sometimes involves significant change. I don’t think we can assume the original architectures put in place were designed to support the utter nuttiness we’re building each and every day. It’s an immensely different landscape now. It seems crazy that these headlines have cropped up in 2013 but it doesn’t take long to look at the Web of today and compare it to the environment in which these rendering engines were born. ![]() They just couldn’t talk about it during their announcement. We can’t forget how tightly related this announcement is to that of Opera just a few short weeks ago they’re using Blink too. If figures from the announcement posts are correct, removal of 7 build systems, 7,000 files, and 4.5 million lines of code is something any programmer would backflip over. Google isn’t happy with a number of factors having to do precisely with significant portions of the WebKit project being directly tied to OS X and/or iOS. The overarching, politics-aside take home message here boils down to performance in my opinion. Once we’re done being experts on the subject, we can take a step back and think about the overall impact here. There are a number of posted reasons for doing so, and it’s up to each of us to determine the honesty and reality of each. The headline that made waves yesterday was that of Google’s Chromium project splitting away from WebKit and forking what is to be called Blink. “But this is different” seems to be the general response at this point, but if we take a step back and look at things a bit more realistically, I think we can all appreciate what’s going on here. ![]() It seems that just yesterday we were terrified of browser monoculture, but today we’re fearful of too much fragmentation. Chromium is actively decreasing the number of Blink public APIs by moving web-platform code from Chromium to Blink (the project is called Onion Soup).This week just got really interesting. Now that Chromium is the only embedder of //third_party/blink/, the API layer does not make sense. In the WebKit era, Chromium and Safari shared the implementation of WebKit, so the API layer was needed to expose functionalities from WebKit to Chromium and Safari. This API layer is just historical artifact inherited from WebKit. ![]() ![]() Content public APIs must be carefully maintained because they are exposed to embedders (that's us!).īlink public APIs are the API layer that exposes functionalities from //third_party/blink/ to Chromium. How Blink Works is a high-level overview doc explaining what it does and how.Ĭontent public APIs are the API layer that enables embedders to embed the rendering engine. Embed Chrome Compositor and draw graphics.Request resources from the underlying network stack.Implement the specs of the web platform (e.g., HTML standard), including DOM, CSS and Web IDL.Roughly speaking, Blink implements everything that renders content inside a browser tab: Blink is a rendering engine of the web platform, which can be found in Chromium's source code under //third_party/blink.
0 Comments
Leave a Reply. |