Microsoft working on new browser, Spartan

Well, didn't see this one coming:

http://www.tomshardware.com/news/micros ... 28270.html

Well, didn't see this one coming:

http://www.tomshardware.com/news/micros ... 28270.html

Indeed.

I am curious to the results of the 'Spartan' browser <img src="{SMILIES_PATH}/icon_cool.gif" alt="8-)" title="Cool">

[quote:hp4ot3wa]Microsoft is digging into Halo lore with the Spartan codename.

<img src="{SMILIES_PATH}/icon_lol.gif" alt=":lol:" title="Laughing">

[quote:2rvg565m]Microsoft is digging into Halo lore with the Spartan codename.

Heh, didn't catch that. I guess somebody snoozed through Greek history.

well, if it is confirmed, that could be nice, maybe a useable alternative to chrome (i know, there is firefox, but 2 concurents are not enough).

You may have not seen that, but I can see all the meme's already.

THIS IS SPAR...SPAR...SPAR...

[quote:745ixehk]Microsoft is digging into Halo lore with the Spartan codename. According to the Halo Wikia, the name describes "members of several super-soldier programs instituted by the UNSC."

Or it could refer to the fact the browser will be lightweight and practical? Like what the word Spartan actually means in modern parlance...

As far as I can tell this is the ordinary IE browser engine (Trident) given a new UI. So it's just a new skin on the same old engine.

However I think the real interesting opportunity is for this new browser to move to a rapid release cycle. That would be great news for ensuring IE progresses as fast as other browsers. However I've also read the bog standard IE11 will still be shipped with Windows 10 for backwards compatibility, so we'll still be juggling various IE versions for some time to come...

[quote:29a0kt1g]

The team behind the engine has forked Trident into two components that will result in a new .DLL when the browser ships.

The forking of Trident, copying off the code base so there are two version, is a strategic move to have legacy support no longer impact modern webpages. How it works, per our internal sources, is that if a page calls for IE to render in a compatibility mode, this will cause the older, more resource intensive Trident engine to display the page. But, if the webpage does not call for compatibility mode, then the updated IE12 Trident engine will handle all of the lifting.

[quote:2jynt4r0]

The team behind the engine has forked Trident into two components that will result in a new .DLL when the browser ships.

The forking of Trident, copying off the code base so there are two version, is a strategic move to have legacy support no longer impact modern webpages. How it works, per our internal sources, is that if a page calls for IE to render in a compatibility mode, this will cause the older, more resource intensive Trident engine to display the page. But, if the webpage does not call for compatibility mode, then the updated IE12 Trident engine will handle all of the lifting.

Wow. That is a really interesting approach. I wonder if there are any plans to extend this back to previous versions of windows, like 7 and 8? Microsoft may like the idea of everyone upgrading en-masse, but I have a sneaking suspicion that 7 is going to end up as tenacious as XP. If this in Win10 only, we're looking at more fragmentation for at least the next few years.