Re:The birth of Microsoft's new web rendering engine
by Mithaldu on Thursday February 26, 2015 @01:41PM
(#9114295)
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:
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.
[ Parent
| on HN ]
Re:The birth of Microsoft's new web rendering engine
by Touche on Thursday February 26, 2015 @02:05PM
(#9114545)
-- 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.
Re:The birth of Microsoft's new web rendering engine
by mkr-hn on Thursday February 26, 2015 @05:10PM
(#9115912)
Everyone forgets the people who created/invented the things Apple puts in its software.
Re:The birth of Microsoft's new web rendering engine
by RoyOfTheEdge on Saturday February 28, 2015 @05:50PM
(#9125343)
-- 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
by gcb0 on Thursday February 26, 2015 @05:56PM
(#9116163)
-- 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
by zanny on Thursday February 26, 2015 @08:56PM
(#9116754)
Konqueror is not abandoned, but Rekonq is generally the premier KDE browser nowadays. Any KDE install still includes Konqueror, even if it is not the default browser, because its backends power a lot of various parts of a KDE desktop.
Re:The birth of Microsoft's new web rendering engine
by path411 on Thursday February 26, 2015 @06:16PM
(#9116241)
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.
Re:The birth of Microsoft's new web rendering engine
by girvo on Thursday February 26, 2015 @07:16PM
(#9116463)
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
by gcb0 on Saturday February 28, 2015 @11:45AM
(#9124170)
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
by path411 on Friday February 27, 2015 @10:37AM
(#9119378)
Firefox didn't make Firebug though. Chrome has supported developers directly a lot longer than Firefox has.
Re:The birth of Microsoft's new web rendering engine
by gcb0 on Saturday February 28, 2015 @11:47AM
(#9124177)
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
by sjwright on Saturday February 28, 2015 @02:18AM
(#9123049)
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
by taf2 on Thursday February 26, 2015 @09:11PM
(#9116792)
"but sadly we have only 3.5 major engines competing at this point." I actually, don't think rendering engine competition is a great thing. I think competing browser products is a great thing. Think about node.js and io.js or rails and merb... it's not necessarily a good thing. Everyone kind of assumes that more rendering engines is good thing but I think it's just important that we have at least one healthy open source option. We have 3
blink webkit gecko
The closed source solutions are the ones we need to hope and pray die away trident. They're evil because there is no hope for any innovation as we saw in the last decade with IE6. MS can do anything they like to re-market their browser but as long as it's closed source engine it has no place in the web IMO. I hope it reaches 1% market share and is forced to go the way of Opera.
Re:The birth of Microsoft's new web rendering engine
by kenko on Thursday February 26, 2015 @04:11PM
(#9115522)
Let's not forget links and w3m.
Re:The birth of Microsoft's new web rendering engine
by indians_pro on Thursday February 26, 2015 @07:44PM
(#9116560)
I'm surprised no one mentioned lynx first.
Re:The birth of Microsoft's new web rendering engine
by kenko on Thursday February 26, 2015 @08:07PM
(#9116618)
I would have mentioned lynx but wasn't sure it still existed.
Re:The birth of Microsoft's new web rendering engine
by icantthinkofone on Thursday February 26, 2015 @05:30PM
(#9116012)
Blink unloads a lot of legacy components in a way that Microsoft is attempting to do now.