Blink is coming to Google Chrome in roughly 10 weeks.
After announcing its departure from WebKit, Google held a Q&A session, which can be seen in the video below.
If you don’t feel like watching all of it, here is a list of questions as well as a timeframe so you can jump to the segment that interests you:
Thanks to Net Applications, we have a fresh set of market share data for you, which doesn’t look that different from the last month, to be honest. Let’s check it out.
Alive and still kicking.
While we wait for the very first build of Opera with Blink, here is something to distract you, at least for a little while.
The changelog itself is minor and includes a couple of bug fixes. However, it’s pretty understandable given the current sitaution.
Hopefully, it’s not made out of cheap plastic.
It seems like a new generation of rendering engines are breeding, which means pretty exciting times ahead, at least for the web browser enthusiasts like ourselves. Developers on the other hand are likely to tremble in fear.
Earlier this week, Mozilla has officially announced a new rendering engine called “Servo”, which (as we wrote back in December) is built using Rust, Mozilla’s own programming language, targeting multi core hardware.
Tune in tomorrow when Opera switches to Trident.
It looks like Apple is about to lose a yet another contributor, at least in the long term. After Google’s announcement that they will be moving away from WebKit, Opera Software announced that they too will contribute and use Blink to power their web browsers.
No more vendor prefixes.
Now here is something that you won’t see very often. Yesterday, Google has announced its plans to “ditch” WebKit and develop their own rendering engine called . Now, before developers get a heart attack, it should be noted that Blink (when it comes to standards) is pretty much a rebranded version of WebKit, at least for now.
So why do it at all? As explained by Adam Barth, the software engineer at Google, it’s all about reducing the complexity and simplifying your overall code base. In fact, it’s estimated that right off the bat they will be able to remove over 7,000 files with a total of 4.5 million lines in code, which says a lot.
Where all these complexities come from? According to Adam, “Chromium uses a different multi-process architecture than other WebKit-based browsers, and supporting multiple architectures over the years has led to increasing complexity for both the WebKit and Chromium projects.”
It’s April already and you know the drill, it’s time to dive into the latest market share numbers from HitsLink.
Follows everyone else.
What could top the upcoming WebGL support? How about SPDY? Thanks to Rafael Rivera, we have learned that Microsoft is actively working on implementing an open networking protocol that was developed by the Google itself.
The good news? Not only will IE11 support it but it seems that the software giant is integrating SPDY to the Windows Blue itself, which means that all store apps can utilize it (and reap performance rewards) from the get go.
Last week, we asked to submit your questions to Alexey Alyarov, the CEO of Zingaya and one of the WebRTC advisory board members.
Well, you asked, he delivered. Enjoy.
Do Not Track arrives as well.
Is it Metro? Modern? Immersive? No one knows yet but the fact is: IE10 Metro is pretty awful and has little to no functionality, just like the earlier Skype builds.
Now, according to WinBeta, IE11 will be at least partially usable as it includes a download list, which can be accessed by clicking on a wrench icon (see screenshot below).