Linked by Thom Holwerda on Wed 29th May 2013 16:59 UTC
Apple At the D11 conference, Apple CEO Tim Cook once again took the stage to be interviewed by Walt Mossberg and Kara Swisher. While most of the interview can be replicated by picking and reading 10 random Apple fanblog stories - there were still a number of very interesting things that warrant some closer scrutiny.
Thread beginning with comment 563265
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Missing Steve Jobs
by Tony Swash on Thu 30th May 2013 22:41 UTC in reply to "RE: Missing Steve Jobs"
Tony Swash
Member since:
2009-08-22

Jobs wouldn't even contemplate opening up anything if he were still around though.



I guess that's why he decided not to make Webkit open source ;)

Reply Parent Score: -1

RE[3]: Missing Steve Jobs
by Tony Swash on Thu 30th May 2013 22:45 in reply to "RE[2]: Missing Steve Jobs"
Tony Swash Member since:
2009-08-22

"Jobs wouldn't even contemplate opening up anything if he were still around though.



I guess that's why he decided not to make Webkit open source ;)
"


I should add that what I liked about Jobs the most was the way he could, apparently with all sincerity, passionately argue one position (example: 'nobody wants to watch video on a small screen') and then pivot 180 degrees on the issue whilst making it look like nothing had shifted. So the whole 'Jobs would block ------' thing is not really right. Jobs would block something until the time came to not block and then he would embrace it - as he did with Apps on the iPhone.

Reply Parent Score: 1

RE[4]: Missing Steve Jobs
by darknexus on Thu 30th May 2013 23:14 in reply to "RE[3]: Missing Steve Jobs"
darknexus Member since:
2008-07-15

I guess that's why he decided not to make Webkit open source ;)

He didn't decide to do that out of the goodness of his heart. Webkit was originally a fork of KHtml, which was and still is licensed under the lgpl. IANAL, but to my understanding, this means that while non-gpl programs can link to a library licensed this way, one cannot hold back source code modifications and still comply with the lgpl. This meant, simply, that in a country such as the US where licenses are enforceable, Apple had no choice but to continue Webkit as an open source project. To do otherwise would have been a violation of the lgpl.
Of course, at that time it was in Apple's best interest to be as open as possible. They were the under dog and, on top of that, trying to work their way up from being damn near dead. As far as general purpose computers go, they're still the underdog and notice that OS X is still as open as it ever was. Contrast this with iOS, where Jobs showed just what he does when his company's on top and allowed his control-freak nature to show. On one hand this kept product quality high, on the other hand it meant a number of artificial limitations. I'm glad to see a possible weakening of some of the more pointless controls, while at the same time I hope the high product quality continues. I want to be able to tweak my iDevices without jailbreaking (custom keyboards, change my default browser, etc), on the other hand I do still want apps to remain sandboxed so as not to corrupt system-wide libraries (saw that on Android once with a Google Maps update, took forever to trace what had happened and fix the entire location stack). Here's hoping for a healthy balance, and I'll raise a glass to that.

Reply Parent Score: 4