Browser war? Sure. But regardless of the improvements MS makes, they still have years worth of a bad reputation they have built up to get over. It will take leaps and bounds for them to ever build up the respect that Mozilla and Google have for building web technology.
The birth of Microsoft's new web rendering engine
71–80 of 247 posts
Re: The birth of Microsoft's new web rendering engine
#72Earlier quoted context omitted.
They can't. They said in a court of law that IE can't be separated from Windows.
But this is another Browser: > This new rendering engine was designed with Project Spartan in mind, but will also be available in Internet Explorer on Windows 10 for enterprises and other customers who require legacy extensibility support.
Re: The birth of Microsoft's new web rendering engine
#73e.g. will the cookie options be something more than a global allow/disallow all cookies?
Will it offer a way to control/block/clear other client-side data, like flash cookies, local storage and so on?
Re: The birth of Microsoft's new web rendering engine
#74This is a powerful paragraph from the article. I'm all for competition, and if they actually produce the next great browser, that'll just mean better browsers overall (and probably even better tooling for us devs). I'm a bit skeptical whether they can pull it off, but at least I have a good feeling that they're out to prove us all wrong.
Re: The birth of Microsoft's new web rendering engine
#75I'm glad to see that Microsoft is finally ripping out all the weird legacy modes -- IE11 essentially ships with 6 different rendering engines! [1] * IE5 (quirks mode) * IE7 (compatibility view) * IE8, IE9, and IE10 (available from the x-ua-compatible meta tag) * IE11's actual rendering engine As an aside, the hilariously long user-agent string is perhaps the best evidence that string-based browser detection is someth…
Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.71 Safari/537.36 Edge/12.0
Glad I don't deal in server-side analytics!
Re: The birth of Microsoft's new web rendering engine
#76I don't see what would entice users to switch from Firefox or chromium or opera (or midori, konqueror, etc) to a new Microsoft browser.
Its probably still worth telling users not to use internet explorer, just in case they ever end up buying a Mac or Linux PC, and out of principle to support free software.
Its good to see competition, but I theorize that this will hurt Mozilla and benefit Google and Microsoft. The quality of chrome has been stagnating recently due to its large market share, while Firefox has been steadily advancing (because Mozilla's primary agenda is to move the web forward). Users have started a slow migration back to Firefox, which I love. A good internet explorer, paired with effective marketing, could threaten chrome and force google to get their act together, ending the Firefox rennaissance.
But realistically I don't see Microsoft marketing this effectively, and internet explorers reputation as a piece of crap will haunt it for years to come.
Re: The birth of Microsoft's new web rendering engine
#77Re: The birth of Microsoft's new web rendering engine
#78FYI. This video has 1 woman, at the end. She doesn't say anything, she just stands there, and she's only visible for a few seconds.
Summing up. Microsoft's new engine, still fighting to gain traction with 50% of the population ;)
Re: The birth of Microsoft's new web rendering engine
#79Re: The birth of Microsoft's new web rendering engine
#80Earlier quoted context omitted.
Citation? IE shipped on Mac until Safari was released.
“Microsoft stated that the merging of Microsoft Windows and Internet Explorer was the result of innovation and competition, that the two were now the same product and were inextricably linked together and that consumers were now getting all the benefits of IE for free. Those who opposed Microsoft's position countered that the browser was still a distinct and separate product which did not need to be tied to the opera…