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.
The birth of Microsoft's new web rendering engine
241–247 of 247 posts
Re: The birth of Microsoft's new web rendering engine
#242Now 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 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
#243Earlier 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.
Re: The birth of Microsoft's new web rendering engine
#244Earlier 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.
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
#245Earlier 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
#246Earlier 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.
Re: The birth of Microsoft's new web rendering engine
#247Earlier 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?