Live data from Hacker News

The birth of Microsoft's new web rendering engine

blogs.msdn.com

111–120 of 247 posts

Re: The birth of Microsoft's new web rendering engine

#111

So fun thing to do in these kinds of videos is to look for women. FYI. 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 ;)

Ridiculous comment.

Re: The birth of Microsoft's new web rendering engine

#113
post #13

Earlier quoted context omitted.

The amount of that article which was focused on legacy was very depressing. When it started to go about how it would break some Little League site that was IE specific that got me very unexcited. Microsoft today needs to learn the lesson of Apple in the very late 90s and just say "no".

They can't. All of the success MS has is based on enterprise - Apple are lucky in not having that restriction. At this point, if MS decided to say F everyone it would come back to bite them very hard. I have a lot of respect to these IE devs for not just quitting and doing something easier, to be honest.

Thank you untog; we're doing our best :)

Re: The birth of Microsoft's new web rendering engine

#114

YES! 1-2-3-4, I declare a browser war! Finally. This is the Microsoft I've been waiting for! No more rolling over and no defeatist talk of adopting WebKit or whatever. Microsoft is going to use its muscle and position to make a truly competitive browser. We need more competition, and we need the default browser in Windows to be just as good as Chrome and Firefox. Microsoft, I hope you pull every -ms- vendor flaggin',…

I'd like to see some competition as well, but in my perspective, they're taking the wrong approach. This entire project seems to be about improving compatibility with older websites, by adding more algorithms and layers to the rendering process. I don't believe everyone is using Firefox and Chrome because they have better compatibility than IE. I think they should focus on cutting the fat, and making the lightest wei…

"If people start to switch over, then more sites will be developed to work in IE Lightning."

Based on this sentence, I get the feeling you don't appreciate the value of web standards? If Microsoft wants to be taken seriously ever again (they had 10+ years to make that effort with IE before they lost the browser war) all they need to do is render pages correctly, not in their own special way. That also means not inventing special-to-Microsoft codes.

Microsoft has a long record of screwing the greater community for their own self-interest. For example, sabotaging Java.

Re: The birth of Microsoft's new web rendering engine

#115
post #71

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.

I don't quite follow your reasoning here. It's got a really bad reputation with devs and people "in the know," but for the average user turning on the computer, it's perfectly fine, and that has to count for something.

Exactly, this is the thing people keep forgetting. IE has a market for people who don't change the default browser from their computers, and it's a good thing they are getting a better, modern browser (not that IE11 is bad, mind you).

Re: The birth of Microsoft's new web rendering engine

#116

YES! 1-2-3-4, I declare a browser war! Finally. This is the Microsoft I've been waiting for! No more rolling over and no defeatist talk of adopting WebKit or whatever. Microsoft is going to use its muscle and position to make a truly competitive browser. We need more competition, and we need the default browser in Windows to be just as good as Chrome and Firefox. Microsoft, I hope you pull every -ms- vendor flaggin',…

Microsoft is going to use its muscle and position to make a truly competitive browser. Isn't this the line with each and every release of IE? Why is this different? Each prior version of IE was proclaimed some revolution of some sort. EDIT: Downvotes? Really? I see the front page is starting to get curiously Microsoft heavy again. We've heard the "this time it's different " argument with IE7, IE8, IE9, IE10, and now…

[deleted]

Re: The birth of Microsoft's new web rendering engine

#117
post #20
post #17

Earlier quoted context omitted.

For Devs to use their browser, sure. But if it is pre-installed on my mom's Windows machine, she'll be using it. They still have that as a huge advantage. So kudos to them for at least trying to correct mistakes legitimately this time.

Their problem is more that it's not installed on Mum's phone or tablet. :)

That's true. I so wanted to like the Windows Phone. I bought a Lumia 1520 and it was a beautiful piece of tech. And I like the default interface of the home screen (Metro works on a phone, not on desktop imho).

But .. then I tried to use the store to get apps and it was a desert. Or the things I could find, worked poorly.

Re: The birth of Microsoft's new web rendering engine

#118
post #106
post #102

I really really hope Microsoft adopts the strategy from competing browsers: - Make one version of Spartan and keep it AUTO-UPDATED, instead of shipping a new version every couple of years that is, more or less, completely decoupled from the previous version. - Decouple the browser from the operating system. I don't really care if they make it cross-platform (though it would be nice), but if the browser stops updating…

> Make one version of Spartan and keep it AUTO-UPDATED, instead of shipping a new version every couple of years that is, more or less, completely decoupled from the previous version. This is what IE 11 currently does, so I would imagine they will continue doing so with Project Spartan.

We have actually been updating Internet Explorer for some years now. We don't touch machines that have opted out of updates, but for everybody else we've been moving them forward regularly.

Spartan is neat because it's a separate app, built on a different architecture that will not only continue to allow us to update in an evergreen fashion, but it will allow us to do so at a much faster rate.

Re: The birth of Microsoft's new web rendering engine

#119
post #106

Earlier quoted context omitted.

> Make one version of Spartan and keep it AUTO-UPDATED, instead of shipping a new version every couple of years that is, more or less, completely decoupled from the previous version. This is what IE 11 currently does, so I would imagine they will continue doing so with Project Spartan.

We have actually been updating Internet Explorer for some years now. We don't touch machines that have opted out of updates, but for everybody else we've been moving them forward regularly. Spartan is neat because it's a separate app, built on a different architecture that will not only continue to allow us to update in an evergreen fashion, but it will allow us to do so at a much faster rate.

I like the fact that you guys are sampling more and more of the web rather than sticking to the top 9K sites. This will make fixing issues in one browser less of an issue (hopefully I'm crossing my fingers).

Re: The birth of Microsoft's new web rendering engine

#120
post #76

But it will still be non-free, and probably won't sync history/bookmarks/open tabs with mobile, except perhaps windows phone. And it only works on windows. I 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…

>Users have started a slow migration back to Firefox

Do you have a source for this? I haven't looked at trends in a while.

Post reply on HN