Live data from Hacker News

The birth of Microsoft's new web rendering engine

blogs.msdn.com

241–247 of 247 posts

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

#241
post #163

Earlier quoted context omitted.

Are you kidding? Firebug was the gold-standard for a very long time, and for a very good reason. If you're talking Firefox's built-in tools, then sure, but talking about Firefox while ignoring extensions is laughable.

Firefox didn't make Firebug though. Chrome has supported developers directly a lot longer than Firefox has.

And Chrome's developer tools were based on the stuff written by Apple for Safari.

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

#242

Now if they could just force this new web browser onto every single Windows XP and later installation out there, so we could get ride of the horrendous amount of IE version < 11 still in use, I would see this in a positive light. The only way I am using IE at the moment if for corporate website that are engulfed in MSFT technologies.

If Microsoft tried that, it would probably end up back in court. Microsoft actually has very little power over its large customers, or those customers wouldn't still be using XP, launched in 2001.

If Microsoft could wave a magic wand then everybody would be on IE11, but it can't. In fact, it can't even make them patch security holes that were fixed years ago.

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

#243
post #163

Earlier quoted context omitted.

What about chrome doesn't respect web developers? Chrome's web debugging in browser is very good, and until recently firefox didn't even compete in that regard.

Are you kidding? Firebug was the gold-standard for a very long time, and for a very good reason. If you're talking Firefox's built-in tools, then sure, but talking about Firefox while ignoring extensions is laughable.

IE invented that. and ie + visual studio to debug JavaScript is years ahead of both chromium and Firefox. does that mean you should now love ie?

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

#244
post #163

Earlier quoted context omitted.

Are you kidding? Firebug was the gold-standard for a very long time, and for a very good reason. If you're talking Firefox's built-in tools, then sure, but talking about Firefox while ignoring extensions is laughable.

Firefox didn't make Firebug though. Chrome has supported developers directly a lot longer than Firefox has.

what's the difference of Firefox doing something vs Firefox enabling people to do something?

the later is actually even better.

also, Firefox has venkman before all that.

sign. kids and Google marketing

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

#245
post #47

Earlier quoted context omitted.

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.

-- Konqueror \ -- Safari \ -- Chrome, Chromium, Opera 15+ If you want to go further Firefox's lineage is interesting but it's parent browsers are all dead.

  -- NCSA Mosaic
    \
     -- Spyglass Mosaic
       \
        -- MSIE
          \
           -- Spartan
I'd be really interested to know how much code from Spyglass or NCSA Mosaic survives in modern versions of Internet Explorer (and even Spartan).

Spartan/IE engineers -- any info?

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

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

Actually it seems strange now, but back in the 90s Apple (and NeXT too) were very focused on the enterprise. They were just "lucky" to have done badly at it. In fact they actually even made servers: http://en.wikipedia.org/wiki/Apple_Network_Server

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

#247
post #183

Earlier quoted context omitted.

Spartan isn't a subset of IE either. We've added support for nearly 50 standards, and more. The delta between IE and Spartan is massive, and growing quickly.

Interesting, if it's a complete fork does that mean IE is not going to be maintained? I thought IE was going to continue on for the time being. If there isn't a common codebase does that mean you're going to be duplicating work? Why?

Internet Explorer will stick around for legacy applications, but Project Spartan uses EdgeHTML (a fork of MSHTML) and is meant to be used with the web moving forward.
Post reply on HN