Slashdot Mirror
The Man Behind Apple And Pixar
Ant writes "Steve Jobs is the chief executive of two of the most powerful technology brands in the world: Apple and Pixar. But what motivates him? And how does he choose a new washing machine? An article in the Independent explores this much loved and much hated man." From the article: "Alan Deutschmann, a journalist who researched Jobs's middle years for a biography called The Second Coming of Steve Jobs, believes he displays two personalities in his dealings with people: Good Steve and Bad Steve. The Good side is charming, and can make people believe almost anything; that's the side on public view at the rock-star product launches. He's been said to have a 'reality distortion field' - by a mixture of charm and exaggeration, he can make you believe pretty much anything."
It took me a while to find what he actually ended up buying. It was a Miele washer. Premium German engineering of course.
In another more detailed interview ,
Steve went on, "It takes a passionate commitment to really thoroughly understand something.... Most people don't take the time to do that." He then proceeded to tell a story that both sheds light on his private life and gives some insight into the decision-making process that often turns life into a hell for people who work with him. Making the point that design isn't just an issue for "fancy new gadgets," he described how his whole family became involved in, of all things, the selection of a new washing machine and dryer. This is a little hard to picture: The billionaire Jobs family didn't have very good machines. Selecting new ones became a project for the whole family. The big decision came down to whether to purchase a European machine or an American-made one. The European machine, according to Steve, does a much better job, uses about one-quarter as much water, and treats the clothes more gently so that they last longer. But the American machines take about half as long to wash the clothes.
"We spent some time in our family talking about what's the trade-off we want to make. We spent about two weeks talking about this. Every night at the dinner table" -- imagine dinner-table conversation about washing machines every night! -- "we'd get around to that old washer-dryer discussion. And the talk was about design." In the end, they opted for European machines, which Steve described as "too expensive, but that's just because nobody buys them in this country."
Of course, this wasn't really about washing machines; it was about passing along the concern for design to his children and perhaps to (his wife) Laurene. The decision clearly gave him more pleasure than you would expect. He called the new machines "one of the few products we've bought over the last few years that we're all really happy about. These guys (had) really thought the process through. They did such a great job designing these washers and dryers."
Steve's surprising tag line on the story says a great deal about how much design really means to him: "I got more thrill out of them than I have out of any piece of high tech in years."
Some people might think it a bit weird that there was so much thought going into buying a washing machine, but i think that if you get to see some of the lovely stuff Miele make you might not think it so weird. It's obvious the engineers at Miele are as obsessive over their machines as Jobs is over his. And it's clear he noticed and appreciated that.
Not to mention how nice it is to know that despite his billions he still does his own laundry.
Jobs could be milking Apple for a lot more than $1 per year, if he was really motivated by money....
http://en.wikipedia.org/wiki/Steve_Jobs
Jobs worked at Apple for several years with an annual salary of $1, and this earned him a listing in Guinness World Records as the "Lowest Paid Chief Executive Officer". At the 2001 keynote speech of Macworld Expo in San Francisco, the company dropped the "interim" from his title. His current salary at Apple officially remains $1 per year, although he has traditionally been the recipient of a number of lucrative "executive gifts" from the board, including a $90 million jet in 1999, and just under 30 million shares of restricted stock in 2000-2002. As such, Jobs is well compensated for his efforts at Apple despite the nominal one-dollar salary.
"These are my principles. If you don't like them, I have others." --Groucho Marx
Their insistence on the "resource" fork always struck me as idiotic: data is data. If it is in a file, it is a bunch of bytes (or even blocks of bytes) -- no need to have separate "meta" information.
Resource forks are sensible given their purpose: to allow strings, in-program graphics, sounds, etc. to be tweaked without having to recompile or have necessary files outside of the application itself.
This way localization and some UI changes could be made without having to know how to change the source directly. Translators that can program are more costly than translators that can fiddle with ResEdit. Early on it was also hoped that files could use them productively (e.g. a text file that was raw text in the data fork, so that lesser systems could still read it, but with formatting in the resource fork) but this didn't really work out.
Application bundles (folders that masquerade as actual programs, and contain all the various resources in separate files) are a different way of accomplishing the same goal, basically. They're not quite as good, since they're known to break and revert back to behaving like folders, but it's better than what you see on other platforms.
At any rate, given that you seem to actually be complaining about metadata, this indicates that you have no idea what a resource fork is and probably never seriously used a Mac. Metadata (which is invaluable) is known on pretty much all platforms to one degree or another. Filenames, permissions, modification dates -- these are all metadata, and may or may not be portable across platforms. The Mac had some additional metadata -- custom icons, file types, which app should open a particular file, etc. -- and it improved the usability of the system. Frankly, we could do with yet more.
Of course, if you like to tell software what sectors on the disk to read instead of using filenames, which are metadata, more power to you. But most people aren't that crazy.
That drove me nuts -- it meant you couldn't easily make tools (as in any Unix environment), because you had to be willing to do resource fork stuff.
Meh. As a rule of thumb, doing a task in software takes a set amount of work. The more work that the programmer does once, the less work that the user will have to do repeatedly. So programming should be comparatively hard, in order to make use quite easy.
Now, the form of use that consists of creating more tools should also be easy, but that requires a hell of a lot of work by programmers to make it so. Recently, Apple has put out Automator, which is handy, but still needs significant work. Applescript was an interesting attempt, but really didn't work out well for most people.
-- This and all my posts are in the public domain. I am a lawyer. I am not your lawyer, and this is not legal advice.
"Insistence" is really the wrong word. After Jobs' return, many of the NeXT developers tried to deprecate such traditional Mac-isms, but the established Mac developer base, as well as many users (especially in the publishing/graphic arts marketspace), balked.
The original point of the resource fork was to provide a system wide "poor man's database" so that any arbitrary application or data file could have arbitrary tagged data appended to it without breaking or confusing apps that originally read the file. For example, to add publishing keywords to a graphics file in its data fork, you have to worry if you are working with a EPS, JPEG, PSD, TIFF or whatever. Each file format has it's own way of storing metadata and added info that are mostly incompatible with each other. However, assuming you are in a mostly Mac-based shop, you can simply add a "IPTC" resource to the file's resource fork, and you have added keyword data without worrying about the contents or exact format of the file in question, even if it's a file format yet to be invented.
After the early virus problems with System 4-6 OSes, Apple tried to start migrating away from resources to trying to develop a form of "universal container" file format. QuickTime's MOV format and disk images are two such stabs. However, this doesn't solve the compatiblity problem with the "outside world" since that just moves the problem from trying to NOT ignore a secondary data stream (that is, the resource fork) to the problem of insuring all file I/O goes through a "standard container file access" library.
it meant you couldn't easily make tools (as in any Unix environment), because you had to be willing to do resource fork stuff. That sort of thing convinced me that the Mac was half-baked, and I should just stick to BSD-derived OSes.
OS X is more or less a BSD-variant. It has more in common with a BSD than the System V derived UNIXes like Linux is alleged to be. As for the tool making problem, under recent OS X releases, you can treat the resource fork of a file like a subdirectory named "/rsrc" in most contexts. This is similar to what Windows needs to access NTFS stream data.
Those who complain about affect & effect on
>> With the fading away of multimedia CDs and what not, iTunes and the iPod are the only thing keeping QT in widespread use.
When looking at the movie/effects etc. industry you will find that QuickTime is by far the most popular way to encode Video. Especially because of all the different codecs supported by default (Pixlet, H264, Animation/Lossless). It's the only format I know of that supports such a wide range of ecoding methods and where you can be absolutely sure that when another person has this package installed, it WILL work.