Live data from Hacker News

The birth of Microsoft's new web rendering engine

blogs.msdn.com

141–150 of 247 posts

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

#141
post #25

Earlier quoted context omitted.

We have a already have lot of competition. In fact, it's never been better: Chrome, Firefox, WebKit, Chromium, Opera. You can even get the source code for Firefox and Chrome and contribute. I'm glad Microsoft is making a better go at it, but honestly, Microsoft could have built a more compliant browser any time they wanted too. https://html5test.com/results/desktop.html

Chrome and friends aren't webkit anymore, but only by way of forking. Otherwise Chrome, Chromium and Opera 15+ are the same engine. The family tree kind of looks like this: -- Internet Explorer -- Firefox -- Safari \ -- Chrome, Chromium, Opera 15+ -- Opera 12 (abandoned) I'm a little unclear on how differentiated Webkit and Blink are in practice, but sadly we have only 3.5 major engines competing at this point.

Blink unloads a lot of legacy components in a way that Microsoft is attempting to do now.

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

#142
post #36
post #25

Earlier quoted context omitted.

We have a already have lot of competition. In fact, it's never been better: Chrome, Firefox, WebKit, Chromium, Opera. You can even get the source code for Firefox and Chrome and contribute. I'm glad Microsoft is making a better go at it, but honestly, Microsoft could have built a more compliant browser any time they wanted too. https://html5test.com/results/desktop.html

Opera, Chrome and Chromium are based off the same engine which is a fork of WebKit. If anything competition has gone down the last couple of years with WebKit based browsers becoming the standard despite its bugs & non-standard behavior. It reminds me of IE6 in its heyday.

No web developer worth his salt writes code for any one browser. You write code to the standard and test in browsers. Anyone doing differently should be fired on the spot. I'm not aware of any professional web developer who does that.

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

#143

Hahaha. Microsoft and Internet are fundamentally incompatible. All you need to do is go to their homepage to see they don't get the Internet. Never have, never will.

Hey at least they removed the hopeless full-page-blocking "would you like to fill in a survey" that was on their HOMEPAGE.. its a start

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

#144

Based on the team pics, it looks like they got rid of individual offices over there. That's too bad.

I'm a developer with Azure. Most of the developers still have individual offices (a few folks are also 'doubled up' in individual offices because of space constraints). Only some teams have moved to an open-space office layout.

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

#145
post #137

Earlier quoted context omitted.

I upvoted this for sarcasm. But upon reflection I think maybe I missed the point. I guess a lot of it hinges on your interpretation of the words "competitive" and "parity". I'm hoping that it means the expression "IE issue" gradually becomes the exception rather than the norm.

These days most of my bugs are Firefox acting differently than I expect it to (though perhaps compliant to standards). I haven't really had to say "IE Issue" unless I was dealing with 8 and lower.

web audio api :/

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

#146

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…

i think that is what they are going against...

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

#148
post #25

Earlier quoted context omitted.

We have a already have lot of competition. In fact, it's never been better: Chrome, Firefox, WebKit, Chromium, Opera. You can even get the source code for Firefox and Chrome and contribute. I'm glad Microsoft is making a better go at it, but honestly, Microsoft could have built a more compliant browser any time they wanted too. https://html5test.com/results/desktop.html

Chrome and friends aren't webkit anymore, but only by way of forking. Otherwise Chrome, Chromium and Opera 15+ are the same engine. The family tree kind of looks like this: -- Internet Explorer -- Firefox -- Safari \ -- Chrome, Chromium, Opera 15+ -- Opera 12 (abandoned) I'm a little unclear on how differentiated Webkit and Blink are in practice, but sadly we have only 3.5 major engines competing at this point.

    -- Internet Explorer 6-8
    -- Internet Explorer 9-10
    -- Internet Explorer 11
    -- Internet Explorer new?

    -- Firefox
    
    -- Konqueror (abandoned?)
      \
       -- Safari
         \
          --Chromium, Opera 15+
             \
               -- Chrome
         \ 
           --IOS safari

    -- Opera 12 (abandoned)

and that's why i use and only advertise firefox. It is the only browser that respect webdevelopers.

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

#149
post #49

> the new engine began as a fork of MSHTML.dll but has > since diverged very quickly Curiously, this means that Spartan will still be able to trace its lineage back to 1992's NCSA Mosiac (in contrast to Mozilla's Servo, which is a greenfield project). I expect that it will be fascinating to compare the two projects as each matures.

Even though little or no code remain, it's a reminder of how much has happened.

Here is post where Marc Andreessen releases the beta (1993):

http://1997.webhistory.org/www.lists/www-talk.1993q1/0099.ht...

That's only ~20 years ago.

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

#150
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.

Probably just anecdotal based on discussions here at HN [1]

[1] https://news.ycombinator.com/item?id=9045305

Post reply on HN