News for hackers. Stuff that matters.
Re:Keeping Safari a secret by georgemcbay on Friday January 04, 2013 @01:46AM (#5006567)
If he is trying to say that, then he has my sincere apologies, but it doesn't read like that, at least to me.

eg. he says "the names of other browser engines", not "the name of the browser engine our code was originally based on".

The "like Gecko" part is a bit of a red herring here and mostly irrelevant, as that is simply what KHTML/Konquerer used in its own UA ("KHTML, like Gecko").

Re:Keeping Safari a secret by guptaneil on Friday January 04, 2013 @01:50AM (#5006577)
The full quote is:

"That allowed me to tweak the string for maximum compatibility with the websites of that time. Which explains why the Safari user agent string has so much extra information in it, e.g. KHTML, like Gecko — the names of other browser engines."

I interpret that as KHTML and Gecko are names of other browser engines that are listed in Safari's user agent string for compatibility purposes.

Re:Keeping Safari a secret by georgemcbay on Friday January 04, 2013 @01:55AM (#5006588)
Fair enough, I'm not trying to suggest this is some grand conspiracy, it just struck me as a funny phrasing given the shared history of the two layout engines.
Re:Keeping Safari a secret by donmelton on Friday January 04, 2013 @02:08AM (#5006623)
I'll be clarifying that shared history in a later post. Specifically, what made me select KHTML/KJS over Gecko and other engines.
Re:Keeping Safari a secret by glhaynes on Friday January 04, 2013 @03:16PM (#5009595)
Will be fascinated to read that. I remember during the keynote when Safari was announced thinking it was bizarre (not to mention risky) that Gecko wasn't used, but, I knew you all must've had your reasons. As a regular user of Safari and/or WebKit on at least five different platforms, I'm rather happy with how it turned out.