Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The birth of Microsoft's new web rendering engine

blogs.msdn.com

Post reply on HN
Print view View original

11–20 of 247 posts

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

#11

Post by leeoniya »

Igglyboo wrote: post #8
leeoniya wrote: post #6

"Fixing patterns instead of sites" I don't understand this statement

They aren't targeting specific sites that are broken they are targeting more general patterns that seem to cause problems.

I understand the language. I don't understand what they mean by "patterns". Common edge cases where js/css/html is broken in specific ways?

If you write html/css in a relatively compliant way, things will not be so broken that a browser vendor needs to account for them in a "long tail". If your js is broken, well tough luck.

Are they just talking about how to implicitly handle commonly malformed HTML, as all browsers do?

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

#12

Post by michaelpinto »

Someone1234 wrote: post #4

I feel like the "A new Web rendering engine is born" section covers quite honestly why they have chosen to fork IE. It seems, to me, to be pretty frank and doesn't contain much "doublespeak." PS - This was originally a reply to a comment which got removed.

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".

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

#13

Post by untog »

michaelpinto wrote: post #12
Someone1234 wrote: post #4

I feel like the "A new Web rendering engine is born" section covers quite honestly why they have chosen to fork IE. It seems, to me, to be pretty frank and doesn't contain much "doublespeak." PS - This was originally a reply to a comment which got removed.

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.

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

#15

Post by EdSharkey »

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', ring-0 kernel hookin', micro-optimizatin', site-specific D3D driver tweakin' trick in the book as you reach for parity. This is going to be so fun to watch.

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

#17

Post by thebouv »

andhof-mt wrote: post #16

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.

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.

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

#18

Post by thebouv »

pdknsk wrote: post #14

It doesn't matter unless they make it open-source or at the very least cross-platform. I'm not downloading a 4GB VM from http://modern.ie to try it.

Honestly, with as much OSS as they've been putting out there recently, I wouldn't be surprised to see this browser go that route too.

Maybe.

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

#19

Post by freehunter »

pdknsk wrote: post #14

It doesn't matter unless they make it open-source or at the very least cross-platform. I'm not downloading a 4GB VM from http://modern.ie to try it.

I think the point is that you shouldn't need to try it. If you write standard code, it should work.

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

#20

Post by heleph »

thebouv wrote: post #17
andhof-mt wrote: post #16

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.

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. :)
Post reply on HN