4 ms·

Pretty surprising that it's coming with a new rendering engine given the good progress Microsoft has been making in bringing Trident in line with the competitio

Pretty surprising that it's coming with a new rendering engine given the good progress Microsoft has been making in bringing Trident in line with the competition.

Touche 12y ago
That's by far the most interesting thing about this, where are the details on that?
Eyas 12y ago
Insiders have reported on this previously. Basically the "new" rendering engine is a fork of Trident which removes backwards compatibility and legacy code. They might call it something else, but the new engine is basically Trident, refactored, and without the legacy cruft. Source: http://www.neowin.net/news/internet-explorer-12-big-changes-are-coming-to-trident http://www.neowin.net/news/internet-explorer-12-big-changes-... Validated by a few other insiders, including Paul Thurrott, Tom Warren (The Verge), and Mary Jo Foley (ZDNet).
- Touche 12y ago
  So in this case fork = rename.
  - Eyas 12y ago
    My understanding is fork = fork + rename. An actual fork did take place, the older branch will continue to be maintained for a separate browser process used by enterprises for compatibility.
  - phaker 12y ago
    Webkit was called called a fork of khtml, if that was a fork then so is this.
wmf 12y ago
Is "new rendering engine" marketing-speak for "Trident with backwards compatibility ripped out"?
- Alupis 12y ago
  I can't be the only person that was really hoping they'd just use Web-kit and help "standardize" how websites render... really tired of having:  Now instead we'll have: 
  - mordocai 12y ago
    Instead? Surely you mean, as well. You'll have to support both IE and SPARTAN. It is just another browser we have to deal with.
    - wolf550e 12y ago
      Every person with SPARTAN will have IE installed too. A site can say "works only in SPARTAN/Chrome/Firefox/Safari" or "Works only in IE" (for different markets).
  - rhengles 12y ago
    Conditional comments were removed since IE10. Not that they've been necessary since IE9... Modern IE is a very decent browser.
- hvs 12y ago
  I don't see how this is any different from calling io.js a "new server-side javascript platform" even though its forked from node. Ripping out the backwards compatibility will do a ton for maintainability and regression testing.
- on_and_off 12y ago
  Yes.

Pretty surprising that it's coming with a new rendering engine given the good progress Microsoft has been making in bringing Trident in line with the competition.

Touche 12y ago

That's by far the most interesting thing about this, where are the details on that?

Eyas 12y ago

Insiders have reported on this previously. Basically the "new" rendering engine is a fork of Trident which removes backwards compatibility and legacy code. They might call it something else, but the new engine is basically Trident, refactored, and without the legacy cruft. Source: http://www.neowin.net/news/internet-explorer-12-big-changes-are-coming-to-trident http://www.neowin.net/news/internet-explorer-12-big-changes-... Validated by a few other insiders, including Paul Thurrott, Tom Warren (The Verge), and Mary Jo Foley (ZDNet).

Touche 12y ago
So in this case fork = rename.
- Eyas 12y ago
  My understanding is fork = fork + rename. An actual fork did take place, the older branch will continue to be maintained for a separate browser process used by enterprises for compatibility.
- phaker 12y ago
  Webkit was called called a fork of khtml, if that was a fork then so is this.

wmf 12y ago

Is "new rendering engine" marketing-speak for "Trident with backwards compatibility ripped out"?

Alupis 12y ago
I can't be the only person that was really hoping they'd just use Web-kit and help "standardize" how websites render... really tired of having:  Now instead we'll have: 
- mordocai 12y ago
  Instead? Surely you mean, as well. You'll have to support both IE and SPARTAN. It is just another browser we have to deal with.
  - wolf550e 12y ago
    Every person with SPARTAN will have IE installed too. A site can say "works only in SPARTAN/Chrome/Firefox/Safari" or "Works only in IE" (for different markets).
- rhengles 12y ago
  Conditional comments were removed since IE10. Not that they've been necessary since IE9... Modern IE is a very decent browser.
hvs 12y ago
I don't see how this is any different from calling io.js a "new server-side javascript platform" even though its forked from node. Ripping out the backwards compatibility will do a ton for maintainability and regression testing.
on_and_off 12y ago
Yes.