21–30 of 52 posts
Looks like it supports both Chrome and FireFox extensions - http://www.theverge.com/2015/4/29/8515771/microsofts-edge-br...
In my humble opinion as an extension developer this is madness. Of course still probably better than rolling out their own. They should stick to a single stack.
Hmm, I don't like this name, it's still trying to be something special. I surmised from the chatter until now that Edge would be called "Internet", "My Internet", or "Browse" or some other non-program entity thing. And quite frankly, that made me shiver a bit for Firefox and (less so) for Chrome. See, what if Microsoft plain-wrapped their browser, made it seamless and ubiquitous? Perhaps this is what they were envisi…
I wouldn't bet on that.
Hmm, I don't like this name, it's still trying to be something special. I surmised from the chatter until now that Edge would be called "Internet", "My Internet", or "Browse" or some other non-program entity thing. And quite frankly, that made me shiver a bit for Firefox and (less so) for Chrome. See, what if Microsoft plain-wrapped their browser, made it seamless and ubiquitous? Perhaps this is what they were envisi…
Yet another engine to support. They are creating their own called EdgeHTML
It's replacing Trident for everyone except companies that use internal software designed for IE6, and you can pretty well ignore those users. Same number of engines to support as before.
Earlier quoted context omitted.
In my humble opinion as an extension developer this is madness. Of course still probably better than rolling out their own. They should stick to a single stack.
Why?
Looks like it supports both Chrome and FireFox extensions - http://www.theverge.com/2015/4/29/8515771/microsofts-edge-br...
So I'm happy if MS is able to break down those walls and take us more toward an open browser standard, as yefim commented.
Earlier quoted context omitted.
IE11 trident rendering engine was already renamed to "Edge", press F12 check it out (then see in the bottom bar -> top right). The step from IE11 to IE12 aka Edge from the render engine is not as huge an outside might think (reading only the PR) - it's still a great step forward so don't get me wrong. The GUI window app has been completely scrapped in favor of a WinRuntime app "Edge" instead of the old iexplore.exe t…
Partially correct. EdgeHTML was in IE11, but wasn't a renamed MSHTML (check your system32, you'll see both DLLs in Win10). It's a departure from MSHTML that's been seriously changed, lots of cruft removed and a lot of interop added. Fun anecdote - last week someone at Steam wrote one of the sale pages using entirely -webkit- prefixes. It showed up blank in Forefox, but rendered fine in Spartan and Chrome.
Looks like it supports both Chrome and FireFox extensions - http://www.theverge.com/2015/4/29/8515771/microsofts-edge-br...
Wow...this kind of levels the playing field. A big reason I stayed away from IE was because of the extensions. If people's favourite extensions start working on Edge, then I'm sure many will give it a serious go.
Till then, stick with Firefox or Chrome.
Yet another engine to support. They are creating their own called EdgeHTML
It's replacing Trident for everyone except companies that use internal software designed for IE6, and you can pretty well ignore those users. Same number of engines to support as before.