By mswatcher
via techcrunch.com
Submitted: Feb 18 2013 / 07:23
The news that Opera is shutting down the development of its own browser rendering engine and moving to the open source WebKit engine caused quite a stir earlier this week. With WebKit powering the built-in browsers of Google’s Android and Apple’s iOS, it’s already the de-facto standard engine for mobile and it has the potential to do the same on the desktop. Worldwide, Chrome now holds a considerable lead over Microsoft’s Trident-powered Internet Explorer and Mozilla’s Gecko for Firefox already. The question is: are we better off because we have competing engines trying to outdo each other, or would we be better off if all the browser vendors just standardized on WebKit?
-
Change the Studio Category of your DevKit Component
-
Reverse engineering your .NET applications
-
How to structure your PHP code to achieve testability and maintainability?
-
Serializing in C++ leveraging template metaprogramming (part iii)
-
Freedom, responsibility, and testing: Lessons for DevOps
-
Windows Phone Toolkit: Context Menu getting selected item within a long list selector
Add your comment
