Earlier this month, Microsoft has published a video to thank developers for their contributions all over the world. Now, it looks like Google too has decided to thank them with (in my opinion) a much better version.
How else can Google demonstrate its superiority? Display how WebP compares to JPEG or PNG, obviously. Without sacrificing the quality, WebP is able to achieve dramatic reduction in size by up to 34% when compared to JPEG and up to 26% when compared to PNG. Continue Reading
Shows an amazing difference in bandwidth and file size.
As the I/O event continues, Google has just compared its VP9 video compression standard to H.264 and as you can see in the slide above, VP9 offered a decrease in size of 63% when compared to H.264, at least in one particular video. Continue Reading
As you might know, Google has recently announced its new rendering engine called Blink, which made us wonder whether or not Microsoft will soon be involved. Why? If you are a Windows Phone user, then there is a high probability that you are already using a photography app by Microsoft Research (first demonstrated in September 2012), which too is called “Blink”. Continue Reading
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. Continue Reading
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.” Continue Reading