Posts with tag browser
It's still Trident, though
The ever reliable Mary Jo Foley of All About Microsoft on ZDNet is reporting that, despite expectations that Microsoft is working on developing Internet Explorer 12, Microsoft is in fact working on an entirely new web browser developed from the ground up using the existing Trident core. The new web browser, which is expected to ship alongside Windows 10 and is codenamed Spartan, sticking with Microsoft’s Halo inspired codenames for the next version of Windows, will feature versions both native to the “Modern” tablet experience as well as the desktop.
Microsoft will reportedly ship Windows 10 with both the new Spartan web browser alongside the existing version of Internet Explorer 11 found on Windows 8.1 devices for backwards compatibility purposes. According to Jo’s sources, “Spartan” will feature a brand new, streamlined, user experience that more closely resembles other modern web browsers, including Google’s Chrome and newer versions of Mozilla Firefox.
Microsoft may not be on track to ship a beta version of “Spartan” in time for the official Windows 10 Consumer Preview in January, however it will likely ship with a future build pushed to Windows Insiders not long after.
Source: All About Microsoft
Pay up or get out
In a seemingly backwards change of policy for Google and their “open-source” Android operating system project (AOSP), we’re hearing of confirmation from developer Maximiliano Firtman that Android 4.4 “KitKat”, the new version of Android that shipped with the new Nexus 5 just a couple of weeks ago, is being published without a web browser. Vendors, who rely on AOSP for the operating system on their phones, are now being forced to license Google Chrome if they want to avoid the headache of developing their own web browsers; previously, Google provided a free “Browser” application with the AOSP that had most of the basic features of Google Chrome for Android.
The change in policy comes as Google hopes to take over increasing control of Android. Google has decided that all future versions of their launcher application will remain exclusive to Android with Android 4.4, with the AOSP providing developers and vendors only the Android 4.3 version, which lacks improved Google Now integration, Google search integration, and more. Google has been under the microscope as of late for their controversial practices, which are seemingly acting against their open source, “don’t be evil” corporate policy.
Coming closer to the WebKit-only web
Fans of Opera (like me) now have some bad news: The Presto rendering engine, which has been used since the very first release of Opera, will be dropped in favour of the WebKit rendering engine, used in other browsers such as Google Chrome and Apple Safari.
The reason for the switch comes down to the fact that most websites these days are written for WebKit, with support for Internet Explorer begrudgingly thrown in. They say they want to push open standards rather than push scripting for specific browsers.
The downside to this is that Opera will become essentially nothing more than a clone of Google Chrome with a different UI and a different add-on API. So if you use Opera, you may as well switch to Google Chrome – the rendering engines will be the same, it’s multi-platform, and it’s rather light on resources.
It, unfortunately, means we’re moving closer to a web that only supports WebKit. Still… at least it will be miles ahead of Internet Explorer.
Update February 13th, 2013 – 12:00 PM CST: Edited the article for clarity.