41–50 of 108 posts
Sure , they wouldn't route back to an Apple IP address but then who's to say Apple doesn't browse via proxy/vpn somewhere?
I distinctly remember how the web dev world (myself included) groaned at the prospect of supporting another rendering engine. Gecko was clearly the best browser at the time, and the choice of KHTML seemed bizarre, to say the least. Even the intention of Apple building it's own web browser seemed weird, Apple had failed at a previous homebrewed browser (Cyberdog), why not just build on top of what Mozilla had already…
We built our own browser because we didn't want to depend on another company for a critical application.
We built our own browser engine because we wanted to use the technology in more things than a browser.
We built that engine small and fast because Bertrand Serlet would have shot me if I had done otherwise. :)
You have to remember that Mac OS X itself was smaller in those days. Not iOS small, but considerably smaller that it is now.
After the initial success of Mac Safari, there was a time when I was second-guessed by some for choosing KHTML and KJS as the basis for WebKit. When we decided to do the iPhone, I was suddenly a genius again. :)
That's just the way it works in the real world.
I distinctly remember how the web dev world (myself included) groaned at the prospect of supporting another rendering engine. Gecko was clearly the best browser at the time, and the choice of KHTML seemed bizarre, to say the least. Even the intention of Apple building it's own web browser seemed weird, Apple had failed at a previous homebrewed browser (Cyberdog), why not just build on top of what Mozilla had already…
I would love to claim the foresight of planning for the iPhone all along. Alas, that was not the case. :) For any of us. We built our own browser because we didn't want to depend on another company for a critical application. We built our own browser engine because we wanted to use the technology in more things than a browser. We built that engine small and fast because Bertrand Serlet would have shot me if I had don…
I found that fact to be the most interesting part of the article. The list of other Class A holders is also interesting: http://www.aturtschi.com/whois/neta1.html
Earlier quoted context omitted.
I would love to claim the foresight of planning for the iPhone all along. Alas, that was not the case. :) For any of us. We built our own browser because we didn't want to depend on another company for a critical application. We built our own browser engine because we wanted to use the technology in more things than a browser. We built that engine small and fast because Bertrand Serlet would have shot me if I had don…
Don, you've had a couple of great stories make it to HN recently -- awesome reads. Looking forward to reading many more.
I distinctly remember how the web dev world (myself included) groaned at the prospect of supporting another rendering engine. Gecko was clearly the best browser at the time, and the choice of KHTML seemed bizarre, to say the least. Even the intention of Apple building it's own web browser seemed weird, Apple had failed at a previous homebrewed browser (Cyberdog), why not just build on top of what Mozilla had already…
By comparison, KHTML was not really a serious project. It had a few developers, but nowhere near the scale of what Mozilla had. Thus, when they forked it to do their work in secret, only a couple people complained.
Earlier quoted context omitted.
Thank you. That was my whole reason for writing it. :)
What are your thoughts on the present and future for Safari? It appears Safari for Windows is all but dead, with no mention of it on Apple's website. Meanwhile Chrome's adoption has been stellar. http://www.w3schools.com/browsers/browsers_stats.asp
Earlier quoted context omitted.
What are your thoughts on the present and future for Safari? It appears Safari for Windows is all but dead, with no mention of it on Apple's website. Meanwhile Chrome's adoption has been stellar. http://www.w3schools.com/browsers/browsers_stats.asp
I'm not going to comment on the present and future of Safari and WebKit. I'm retired. I have no business doing that. And it would disrespect the fine people at Apple -- my friends -- who are still working on both.
Then again it doesn't seem Apple do that very often, cough Do not disturb cough ;)