HN user

donmelton

543 karma

Just another Web geek playing with the Web

http://donmelton.com/

@donmelton on Twitter and App.net

Posts0
Comments38
View on HN
No posts found.

The original options we had weren't restricted. Also, most of them were at a lower strike price since Apple wasn't highly valued then.

Yeah, there was nothing devious there. I hope.

The line about my son was partly to annoy him since he, unlike my wife, reads my blog. And we punk each other like that all the time.

My son, unlike my wife, reads my blog. That's in there just to tweak him. We punk each other like that all the time.

Closure — that's actually a very good way to put it. I didn't feel burned out. Just tired and complete.

But I was very fortunate to have the means to retire. Many who experience burnout don't have that choice. Which is another reason there's such churn in this business.

As a manager, one thing I always watched for were the signs of burnout. I always said I spent way more time coaching people to pace themselves than to work harder.

That's just me being facetious. Don't read that much into it.

Apple was an excellent place to work and I had a great relationship with Scott, Bertrand, Avie and Steve. Nobody was going to shoot me. AFAIK. :)

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.

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

The string was originally just contained "WebKit." When it became "AppleWebKit" in mid-December (as I recall) then, yes, it was more likely to be discovered. But I felt that a 17.x.x.x address would be the clincher and the secret would be out.

I'll be clarifying that shared history in a later post. Specifically, what made me select KHTML/KJS over Gecko and other engines.

I don't know whether the Apple IP addresses were reallocated. I do know that Stanford returned most of its Class A allocation.

Firefox wasn't a big factor when Safari debuted. And the project was still called "Phoenix" back then. I believe that other Mozilla and Gecko-based browsers were more widely used at that time.