There are two meanings to XHTML: technical and marketing. The technical kind (XHTML served using the application/xhtml xml MIME type) is a formulation of HTML as an XML vocabulary. The marketing kind (XHTML served using the text/html MIME type) is processed just like HTML by browsers but the authors attempt to observe slightly different syntax rules in order to make it seem that they are doing something newer and shinier compared to HTML.
Update: Fireballed. Here’s the version in Google’s cache.
]]>
I’ve never encountered a serious client who chose not to use WordPress because it was GPL-licensed, and I think it’s hard to argue that WordPress’s license has had a dampening effect on its adoption, given its success over competitors with widely varying licenses.
I think we have an incredibly strong third-party extension, plugin, and theme community that has flourished, not in spite of the GPL license, but because of it.
I’ve seen the absence of GPL in practice; there have been times in the WordPress world when parts of the community have “gone dark” and claimed their code was under more restrictive licenses, like used to be common with themes. Every time this cycle starts it basically kills innovation in that part of the WordPress world until people start opening up their code again or until a GPL equivalent is available. I’ve seen this firsthand several times now.
I can’t speak for Jalkut, but none of these three points from Mullenweg address Jalkut’s argument.
Jalkut wasn’t arguing about whether users will not use GPL software; his argument was about developers.
Jalkut never argued that WordPress wasn’t popular or didn’t have a strong extension/plugin/theme community. Jalkut’s argument was that WordPress might have an even stronger extension/plugin/theme community if it were licensed under a BSD-style license.
Jalkut wasn’t arguing in favor of more restrictive licenses; he was arguing in favor of less restrictive ones: BSD/MIT/Apache style ones.
In some sense, Jalkut’s essay could be considered a big “Duh” — a statement of the obvious. To wit: that GPL-licensed software projects discourage participation from developers working on anything other than other GPL-licensed software projects. That’s pretty much the stated goal of the FSF. BSD-licensed projects encourage participation from developers working on just about anything.
]]>Prowl is a Growl client for the iPhone. Notifications from your Mac can be sent to your iPhone over push, with a full range of customization and grace you expect.
Great idea. This opens up iPhone push notifications for anything you can think of.
]]>City officials will soon debut Boston’s first official iPhone application, which will allow residents to snap photos of neighborhood nuisances - nasty potholes, graffiti-stained walls, blown street lights — and e-mail them to City Hall to be fixed.
(a) This sounds like a neat idea. (b) The iPhone is turning into a de facto standard platform.
]]>“There’s a massive misperception that incandescents are going away quickly,” said Chris Calwell, a researcher with Ecos Consulting who studies the bulb market. “There have been more incandescent innovations in the last three years than in the last two decades.”
Necessity, once again, is the mother of invention. (Via Dan Benjamin.)
]]>There is one diversion on the Pre that’s really great, but you’ll definitely want to be plugged in while you use it: Sprint TV. The live TV streaming to the device works quite well, and I got a huge kick out of watching ABC News and some reality TV shows on my phone. But I estimate (I haven’t formally tested) that I could stream about 30 minutes of TV to the Pre before completely nuking the battery.
Streaming video involves both playback and constant network use, but 30 minutes sounds shockingly low.
]]>]]>Is anyone really confused about Mr. Jobs’s health status? I remain unconvinced, in part because I believe that prurience, not legitimate financial concerns, drives most people’s interest in the illness of others.
A monorail train at Walt Disney World crashed into the back of another train early Sunday, killing one driver, according to an amusement park spokesman and a witness interviewed by CNN.
Here’s amateur video of the scene just after the accident, shot from the passenger platform at the Ticket and Transportation Center.
Update: Here’s the best speculation I’ve seen explaining how it could have happened, from someone who claims to be a former monorail employee.
]]>If you need further convincing, check out the adorable guided tour video they made to promote the iPhone app’s release last month. Hand-crafted stop-motion animation. If this video doesn’t make you smile, you’re not hooked up right. Imagine how much work went into the app if they put this much work into the video.
]]><video>
tag in Firefox 3.5, you need video files encoded in the Ogg Theora format. Apple doesn’t support this format at all, so you can’t just export Ogg files from QuickTime like you can with H.264/MPEG-4. I spent some time trying to find the best easy way to create Ogg Theora files on Mac OS X, and I think ffmpeg2theora is it.
In his “Video for Everybody” article I linked to yesterday, Kroc Camen suggests using HandBrake to create Ogg Theora files, but I couldn’t get it to work in HandBrake 0.9.3 (the current release version) without crashing. (Well, one time it created a file without crashing, but the file was corrupt.) It ends up that HandBrake’s broken Ogg support is a known issue with no easy solution, and so Ogg support has been removed from the current branch of HandBrake, and there are no plans to bring it back.
Camen also linked to Xiph, an open-source QuickTime component that adds Ogg Theora playback and export to QuickTime. I don’t want to install this, however. For one thing, the only open-source QuickTime component I’ve ever had a good experience with is Perian. For another, I don’t want Ogg playback support in QuickTime. The fork in supported codecs for the <video>
tag — Safari won’t support Ogg Theora and Firefox and Opera won’t support H.264 — doesn’t mean you can’t support all three browsers. It just means that to support all three, you need to include at least two <source>
elements within the <video>
tag, one pointing to an H.264-encoded file, the other to an Ogg Theora file, like this:
<video>
<source src="example-video.mp4" type="video/mp4" />
<source src="example-video.ogv" type="video/ogg" />
</video>
This serves the H.264 to Safari, the Ogg Theora to Firefox. And for Chrome 3.0, which supports both formats, this should serve the H.264 version because it’s specified first.
ffmpeg2theora is the one tool I found that simply just works for transcoding to Ogg Theora. The downside to ffmpeg2theora is that it’s only available as a command-line tool. But:
It has a nice Mac OS X .pkg installer. Launch it, authorize it with admin credentials, and it’ll install the ffmpeg2theora
tool in /usr/local/bin/.
The command-line syntax could not be simpler. You just type:
ffmpeg2theora example.m4v
and it gets to work, outputting a file named example.ogv right next to the .m4v file. It shows an updating progress message in Terminal while it’s working. There are more options (and it comes with a man page that documents them), but in my testing you can just use the defaults.
ffmpeg2theora’s output looks good. I gave it a 3.9 MB H.264 file as input, and it created a 3.5 MB .ogv file that looked pretty good — way better than typical web video in a Flash player — when I played it back in VLC and Firefox 3.5.
]]>Quasimodes require the user to do several things at the same time, such as holding down the Shift key while typing. Modes, on the other hand, allow users to do things sequentially — hit Caps Lock, type, hit Caps Lock again. Sequential actions, especially if guided well, are often easier to execute than parallel actions.
And he argues (correctly, I say) that the iPhone’s new modal interface for selecting text is superior to the WebOS’s quasi-modal interface.
]]>]]>The Loop has confirmed that if your iPhone has a broken screen and you take it to an Apple retail relocation, they have the capability to fix it on the spot. The machine, which is located out of customer view in the back of the store, reportedly separates the iPhone from the screen, allowing a new one to be installed.
Of course, your screen doesn’t have to be completely smashed to need some sort of replacement done. Some users have reported dust particles on the inside of the screen as well.
]]>On this year’s launch day, iPhone sales exceeded sales recorded on 2008’s iPhone launch day, Black Friday 2008 and Dec. 26, 2008 — all heavy-volume sales days. In fact, this year we surpassed 2008’s launch day sales at about noon Central time, and sustained our previous peak hour record, also set in 2008, for 11 straight hours.
<video>
tag, it falls back on Flash, QuickTime, and Windows Media.)
]]>But, alas, the result is an impasse. Apple won’t support Ogg Theora, and Mozilla and Opera won’t support H.264. (Google, admirably, is willing to support both in Chrome, but they don’t consider Ogg good enough to use for YouTube.) So there will be no standard HTML 5 video codec. So it goes.
(Let it be said that Ian Hickson is the Solomon of web standards; his summary of the situation is mind-bogglingly even-handed and fair-minded.)
]]>In the course of reading Chris Anderson’s new book, Free: The Future of a Radical Price (Hyperion, $26.99), for a review in an upcoming issue of VQR, we have discovered almost a dozen passages that are reproduced nearly verbatim from uncredited sources. These instances were identified after a cursory investigation, after I checked by hand several dozen suspect passages in the whole of the 274-page book.
Jaquith includes half a dozen incriminating examples. Plagiarism is a strong word, but there’s no other way to describe some of these passages.
Anderson has responded, acknowledging it as a “screwup”, on his Long Tail weblog.
]]>This ant is composed of 400 pictures, and it’s magnified 400x using a scanning electron microscope. The ant was given to us to image by Brian Fisher an entomologist at the California Academy of Sciences.
The intersection of horrifying and wonderful.
]]>See you next Friday, July 10.
]]>Yes, iPhone = my computer, and $399 is worth it. Haven’t bought new laptop since late 06 and don’t plan to for long time.
This, to me, gets to the heart of the revolution at hand. A decade ago, my first PowerBook was a secondary machine to the desktop anchored at my desk. Now, my main machine is my MacBook Pro, but it feels a bit like an anchor now. My mobile secondary computer is my iPhone.
]]>Can’t wait for the sequel starring Mickey Mouse. (Via Brian Ford.)
Update: Ends up the App Store review team simply doesn’t deal with copyright and trademark verification (with the exception of enforcing Apple’s own trademarks, of course). Any beef Nintendo has (and trust me, they’re going to have a beef with this app) is between Nintendo and Mariolife’s developer. Makes sense.
]]>(And if display advertising is more your bag, this tweet from my friend Jim Coudal may be of interest.)
]]>On a related point, several readers have asked why I seem opposed to Anderson’s view, given that I’ve made a nice career for myself by giving away my own writing for free here on Daring Fireball. My answer to that is that Daring Fireball is decidedly not free. It’s simply a question of who gets charged. Readers don’t, but sponsors and advertisers do. What makes it work so well (so far) is that this makes everyone happy. I’m earning a nice salary. Readers get to read my writing in exchange for a small portion of their attention which I direct toward ads. And sponsors and advertisers are happy to pay a fair price to reach an audience of good-looking, intelligent readers such as yourself. But there’s nothing free about it.
]]>Craigslist Map Thingie slurps housing listings from Craigslist and plots them on Google Maps, with a panorama view of the property, if available.
Update: It’s news to me, but a slew of DF readers emailed to point to Housing Maps, which does something similar.
]]>The consumer electronics wizards at Dell who brought us the now defunct DJ Ditty MP3 player and the Axim handheld are hard at work on another gadget, a mobile Internet device. Sources tell The Wall Street Journal that the MID uses an ARM-based chip, runs Google’s Android operating system and has been in development since last year.
It’s funny, of course, because the DJ and Ditty were huge failures, but when they debuted, many pundits predicted they would topple the iPod. But I hope this rumor is true. I’d consider buying an iPod Touch-like Android device — something for $200 or so, without any sort of monthly phone contract.
Update: To be clear, the reason I’d consider buying a $200 non-phone Android device is so I could use, try, and write about Android apps. Same goes for WebOS, by the way.
]]>Across product lines I see a consistent trend: More of the same, only better.
With insight this deep it’s hard to believe Wilcox was laid off from eWeek.
]]>One way I use my iPhone to actually “work” is with Movable Type’s excellent iPhone-optimized web app interface, with which I can post and edit items to Daring Fireball. I wouldn’t want to write a full-length essay with my thumbs, but it works great for posting short Linked List items.
I post new links to DF from my iPhone more frequently than you might imagine. I no longer lug my MacBook Pro around during the day at conferences such as WWDC, for one thing, and my iPhone is often all I have with me when I’m traveling with my family. Just about any time I’m out of my regular routine, it’s all iPhone, all day.
The basic post-to-DF-from-my-iPhone workflow is like this:
I have a page open in MobileSafari that I want to post as a link to DF.
I invoke a customized bookmarklet in MobileSafari. This bookmarklet sends me to the “create new entry” page on my installation of Movable Type, with the fields for the entry title and link URL pre-populated with the title and URL of the page in MobileSafari to which I’m linking.
I almost always edit the title, but the big score is having the URL field populated automatically by the bookmarklet. Prior to the arrival of copy-and-paste in OS 3.0, the only other way I could have gotten the URL from one page in MobileSafari to the link URL field in Movable Type in a second page in MobileSafari would have been to type it out by hand — painstaking and error-prone.
And but then what about creating additional links within the body of the entry? In those cases I was stuck doing it the pain-in-the-ass way. More often than not, I’d just not add any additional links to the entry, even if I wanted to.
And blockquotes — cited passages from the page being linked to — were pretty much out of the question. Without copy-and-paste, the only accurate way to quote even just a few sentences from one web page and insert them in the DF entry would have been to transcribe the passage by hand with paper and pen, then re-type the passage on the iPhone.
The copy-and-paste implementation in iPhone OS 3 has put an end to that. It’s everything I hoped for, and I use it all the time.
Do I wish this had been in the iPhone all along? Or that it had come a year ago in iPhone OS 2? Sure. But, as I wrote two years ago, given the way that most simple gestures had already been assigned in the iPhone OS user interface, it wasn’t obvious or easy at all to see how text selection and copy/paste should have been added to the iPhone. (And as much as I wanted the feature, I fully realized that most iPhone users don’t publish full-time weblogs and therefore didn’t need the feature nearly as much as I do.)
The two main problems Apple needed to solve were (a) how to allow for the selection of a range of text, and (b) how to invoke cut/copy/paste commands on a system without a keyboard and without a menu bar. Their solution to (a) was to make selection an extension of the existing magnifier loupe interface for placing the insertion point. Their solution to (b) was to present the commands in what is effectively a pop-up contextual menu that appears only when you have made a selection or moved the insertion point.
It all seems fairly obvious once you’ve used it, but there was nothing obvious about it before it was designed. This is one area where Palm, in designing the WebOS interface, couldn’t study what Apple had done (because Apple hadn’t shown it yet) and had to devise their own implementation. Despite the numerous fundamental similarities of the iPhone and WebOS interfaces, text selection and Cut/Copy/Paste are quite different on the Pre. (And, I must say, in my 30 minutes or so of tinkering on the Pre, inferior to the iPhone’s, especially with regard to selecting text.)
That we had to wait two years for the iPhone’s text selection and pasteboard is a good example of one aspect of the Apple way: better nothing at all than something less than great. That’s not to say Apple never releases anything less than great, but they try not to.2 This is contrary to the philosophy of most other tech companies — and diametrically opposed to the philosophy of Microsoft. And it is very much what drives some people crazy about Apple — it’s simply incomprehensible to some people that it might be better to have no text selection/pasteboard implementation while waiting for a great one than to have a poor implementation in the interim.
It’s hard to prove that good is the enemy of great, but the evidence speaks for itself.
I wouldn’t recommend running beta iPhone OS releases on one’s main iPhone for the faint of heart. You get what you ask for if you run into trouble. ↩
Cue your favorite clip of Orson Welles pitching Paul Masson wine: “We will sell no wine before its time”. ↩
Today the Times has a follow-up by Brad Stone and Ashlee Vance, but rather than making the story about Jobs, it’s ostensibly about Apple’s company-wide “obsession with secrecy”. Four paragraphs down, though, comes this:
But even by Apple’s standards, its handling of news about the health of its chief executive and co-founder, Steven P. Jobs, who has battled pancreatic cancer and recently had a liver transplant while on a leave of absence, is unparalleled.
Mr. Jobs received the liver transplant about two months ago, according to people briefed on the matter by current and former board members. Despite intense interest in Mr. Jobs’s condition among the news media and investors, Apple representatives have declined to address the matter, reciting with maddening discipline only that Mr. Jobs is due back at the company by the end of June.
Mr. Jobs was actually at work on Apple’s sprawling corporate campus on Monday, according to a person who saw him there. Company representatives would not say whether he had returned permanently.
So, note that the Times still does not have a first-hand source for the news regarding Jobs’s purported liver transplant. Read the sourcing carefully: according to people briefed on the matter by current and former board members. That’s second-hand information — “people” who were told about it by board members who know about it. (I wonder who the former board member(s) could be? Apple hasn’t had much turnover on the board in recent years. And why would a former board member know about Jobs’s current health status? Curious.)
I also don’t see how Apple’s handling of news related to Jobs’s health is “unparalleled”. They’re no more secretive about his health now than they have ever been. If anything, the low point was a year ago, when Apple PR stated that Jobs’s gauntness was the result of complications from “a common bug”.
And then this:
Even senior officials at Apple fear crossing Mr. Jobs. One official, who is normally more open, when asked for a deep-background briefing about Mr. Jobs’s health after the news of the transplant had become public, replied: “Just can’t do it. Too sensitive.”
Translated into plain English, this is the Times’s acknowledgement that they couldn’t get anyone to talk to them about Jobs, even on “deep background”, which term Wikipedia describes thusly:
“Deep background” This term is used in the U.S., though not consistently. Most journalists would understand “deep background” to mean that the information may not be included in the article but is used by the journalist to enhance his or her view of the subject matter, or to act as a guide to other leads or sources. Most deep background information is confirmed elsewhere before being reported.
In other words, no one at Apple would give reporters from the Times jack shit regarding Jobs’s health. And yet the Times story seems to portray this unwillingness on the part of top Apple executives to betray Jobs’s trust and privacy as something other than admirable.
The rest of the article details specific examples of Apple’s policies for guarding the details of products in development; the implication is that Apple is a weird and creepy place because they try to keep a lid on secrets.
Here’s one example:
Philip Schiller, Apple’s senior vice president for marketing, has held internal meetings about new products and provided incorrect information about a product’s price or features, according to a former employee who signed an agreement not to discuss internal matters. Apple then tries to track down the source of news reports that include the incorrect details.
I’m not disputing that Schiller and Apple do this. But, as someone who has published one or two original nuggets of information regarding upcoming Apple products, I can say that I’ve never seen evidence of it. I’ve never received information from an Apple employee that turned out to be false.1
I can’t help but feel that this story is a rather transparent lashing out on the part of the Times. They couldn’t get any original information regarding the story they really want — Jobs’s liver transplant — and so like a child throwing a tantrum when it doesn’t get its way, they wrote a story about how there’s something wrong with Apple because its employees keep their mouths shut.
Apple’s decision to severely limit communication with the news media, shareholders and the public is at odds with the approach taken by many other companies, which are embracing online outlets like blogs and Twitter and generally trying to be more open with shareholders and more responsive to customers.
So, yes, undeniably, Apple does not communicate via weblogs. I too think they should. I like Google’s approach to official blogging — they don’t write about upcoming products and services, but they do write about the new things they release, offering insight and tips into how and why to use them. (Google is pretty damn secretive about things like upcoming products and the details of its operation infrastructure.)
But: what’s the argument for how Apple has suffered for its secrecy? Yes, Apple is far more secretive than most companies, but they’re also far more successful. Measured by profit and revenue and growth, wouldn’t it make more sense to argue that most companies should act more like Apple, rather than the other way around?
False information I’ve received tends to come from third parties; for example, several iPhone case manufacturers were convinced that Apple was going to announce a smaller “iPhone Mini” at WWDC this month. ↩
Friday night around midnight, The Wall Street Journal published a report headlined “Jobs Had Liver Transplant”1 by Yukari Iwatani Kane and Joann S. Lublin. It stated:
Steve Jobs, who has been on medical leave from Apple Inc. since January to treat an undisclosed medical condition, received a liver transplant in Tennessee about two months ago. The chief executive has been recovering well and is expected to return to work on schedule later this month, though he may work part-time initially.
What’s intriguing about this story is not the question of whether Jobs actually had a liver transplant. I do not doubt that (although I’d like to see better sources for it). What is intriguing is the question of who leaked this information to the Journal and why.
There are several highly unusual aspects to the Journal’s story. First is that they offer no source for the information — not even an “according to sources familiar with the matter”. But yet they state it flatly as certain fact that Steve Jobs had a secret liver transplant in Tennessee. Blockbuster news with no sourcing whatsoever. To call that curious is an understatement. And, coming in the opening paragraph of a page one story, it could not be a careless omission.
The basic tenets of journalism are simple. One reports facts and how one knows them. The principle is much like that of publishing scientific papers, where one describes not just the results, but also exactly how the results were obtained, so that others can reproduce them. This is why named sources are so much more valuable than anonymous sources; with a named source, other reporters can contact the source to verify the information.
But there’s an apt journalism adage from Lord Northcliffe: “News is what somebody somewhere wants to suppress; all the rest is advertising.” And so sometimes the only sources for certain information are those who cannot or will not allow their names to be used. Most publications, and certainly all publications of the stature of The Wall Street Journal, have strict guidelines covering the use of anonymous sources. My friend Matt Deatherage (publisher of the estimable MacJournals) quoted the following from the Journal’s own Wall Street Journal Guide to Business Style and Usage in a post to the MacJournals-Talk mailing list:
ANONYMOUS SOURCES: Accepting a source’s request for anonymity sometimes is the only practical way to obtain important information, but we must be circumspect. On-the-record sources are always preferable because they may be held personally accountable for what they say and are therefore generally more certain to be scrupulously accurate. Also, readers are able to make judgments about the reliability of those whose identities are provided.
In cases where the person’s identity is to be protected, take pains to indicate where his or her biases might lie: “an executive working for a competitor … an executive who left the company in a management shakeup … a laid-off employee …” or “a close relative of the plaintiff.”
Their story on Jobs’s purported liver transplant offers no sourcing for the reader to judge. It entirely hinges on the (admittedly significant) credibility of The Wall Street Journal itself.
Again, I point all this out not to say that I don’t believe their report. I’m as big a cynic regarding anonymous sourcing as anyone, but I believe that Jobs indeed had a liver transplant in Tennessee simply because The Wall Street Journal has placed its credibility behind the story. There is no hedging or fudging in their report. If it’s not true, it would amount to one of the biggest mistakes in their esteemed history.
But reputable news publications do not ordinarily report utterly unsourced news. (I cannot find another example of the Journal reporting completely unsourced page one news.) So: why?
Most major news publications have picked up the story, but only by sourcing the information to the Journal itself. For example: Bloomberg, The San Jose Mercury News, ABC News, and The BBC. Bloomberg’s report is indicative of this second-hand reporting:
Steve Jobs, co-founder and chief executive officer of Apple Inc., underwent a liver transplant two months ago, the Wall Street Journal reported, without disclosing the source of the information.
Even The New York Times has published a piece (“Apple Chief Reportedly Had Liver Transplant”) but they too have no source for the news other than the report in the Journal. (Surely the Times has reporters digging into this story; the aforelinked piece crediting only the Journal ran almost 24 hours after the Journal’s story, and as of this writing, four hours later, has not hit the front page of nytimes.com.)
The only publication claiming independent verification is CNBC, late Saturday night:
Two sources confirmed to CNBC that Jobs had the surgery and another confirmed that his plane flew from San Jose to Memphis in late March.
Further curiosity: whoever the Journal’s source, they didn’t give the WSJ any publishable information regarding why Jobs needed a new liver — that part of the article is pure speculation, quoting doctors who have never treated Jobs personally. Is it because the Journal’s source doesn’t know, or because the source wouldn’t tell? There’s a big difference.
There have been rumors circulating for months that Steve Jobs had moved to Tennessee for some sort of medical treatment. Here’s a rumor Barron’s Tech Trader Daily published on April 15, which in turn cites a report by Alexander Haislip of the PEHub Blog (which does not have publicly available archives). Haislip wrote:
I spoke with a well-connected business person in Memphis this morning who says that there is a house in a swank neighborhood there that has been bought for a princely sum and is undergoing minor renovations in preparation for its new resident.
He says he has reason to believe Apple CEO Steve Jobs is moving to the city to treat his pancreatic cancer.
Several readers sent me this Barron’s link back when it was new, but I decided against linking to it because it was just so sketchily sourced. (And even now, if the WSJ report turns out to be completely accurate, the Barron’s rumor was wrong with regard to the treatment for which Jobs went to Tennessee.) I’ve ignored a slew of Jobs-related rumors over the past year because of the sourcing.
One thing that struck me as wrong at the outset regarding these “Jobs-in-Tennessee” rumors is the question of why he’d bother going to Tennessee in the first place. Tennessee may be a lovely state, but, well, it doesn’t sound like Steve Jobs country. You don’t need to leave the Bay area to get world-class medical treatment. The Journal’s report has a good answer:2
The specifics of Mr. Jobs’s surgery couldn’t be established, but according to the United Network for Organ Sharing, which manages the transplant network in the U.S., there are no residency requirements for transplants. Having the procedure done in Tennessee makes sense because its list of patients waiting for transplants is shorter than in many other states. According to data provided by UNOS, in 2006, the median number of days from joining the liver waiting list to transplant was 306 nationally. In Tennessee, it was 48 days.
But if the Journal knows that Jobs had a transplant, and knows that it was performed in Tennessee, why don’t they know which hospital? Again from their report:
Three hospitals in Tennessee — Le Bonheur Children’s Medical Center in Memphis, Vanderbilt University Medical Center in Nashville and Methodist University Hospital in Memphis — are designated as liver-transplant centers, according to UNOS. A spokeswoman for Le Bonheur said the hospital doesn’t perform liver transplants in adults. A Vanderbilt spokesman said it didn’t treat Mr. Jobs. A spokeswoman for Methodist University said Mr. Jobs isn’t listed as a patient there.
Reading between the lines, if Jobs had a liver transplant in Tennessee, it must have been at one of these three hospitals. Two flatly deny it, but the third, Methodist University, simply stated Jobs “isn’t listed as a patient” — present tense, not past tense. So it must have been performed there. But why can’t the Journal state that as fact as well?
That this news broke months after the purported transplant, at midnight on the Friday of what appears to be the most successful new product launch in Apple history, strikes me as beyond coincidence. My first thought was that it must be a deliberate, timed leak from Apple. Assuming the story is true and that Apple felt the need to eventually release the news, when better to release it than on the very day when it most appears that Apple has continued to thrive while Jobs was on medical leave? MG Siegler at TechCrunch speculates similarly:
We’d be remiss if we didn’t note that the timing of this story appears favorable for Apple. This news breaks late on a Friday, after Apple has just held a successful launch of a very high profile new product, the iPhone 3GS, that sent the stock soaring today. Obviously, the market won’t be open again until Monday.
I don’t see how the leak could have come from someone with a competitive interest against Apple. The timing is completely favorable to Apple; if the leak had come from someone wishing ill against Apple, it would have come at some time, any time, other than in the wake of the extremely successful iPhone 3GS launch. Plus, other than the surprise that Jobs had a liver transplant in the first place, the gist of the article is largely favorable to Apple. It emphasizes that Jobs is recovering, is still set to return to work this month, and has already been seen on Apple’s campus recently. It is also the case that it would be unconscionable for the information to come from someone with a position against Apple and for the Journal not to describe the source as such.
Thus I see only three possible sources for the leak.
Theory 1: That the information came without Jobs’s permission or knowledge, from a healthcare provider with knowledge of Jobs’s medical situation. Presumably, given the Journal’s report, from someone at Methodist University Hospital in Memphis. Such a leak would clearly be a violation of HIPAA privacy laws. This might explain the utter lack of sourcing and the certainty as to the veracity of the information, but it would not explain the perfect-for-Apple timing of the leak, which timing I firmly believe is simply too convenient to be coincidence. It would also raise serious questions regarding the ethics of the Wall Street Journal. I therefore discount this possibility.
Theory 2: That the leak was authorized by Jobs himself. I doubt Jobs personally spoke to the Journal reporters (see below), but it could have been someone close to him (if so, I’d guess Katie Cotton or someone else high up in Apple Communications) doing it with his permission. The thinking behind this theory would be that if the information was going to become public eventually, why not control it and have it come out at the most advantageous time possible. This scenario would explain the certainty of the information, but not the odd lack of sourcing.
My thoughts then ran to the possibility that perhaps Jobs himself is the source — he has occasionally called reporters personally. And if he offered the information only on the condition that it not be sourced to him by name, perhaps the Journal couldn’t bring themselves to describe Jobs himself as merely “a source familiar with the situation” or somesuch. But the second paragraph in the Journal story seems to preclude Jobs personally as the source:
Mr. Jobs didn’t respond to an email requesting comment. “Steve continues to look forward to returning at the end of June, and there’s nothing further to say,” said Apple spokeswoman Katie Cotton.
That language leaves the clear impression that Jobs did not personally contribute to the report, and it implies that Katie Cotton did not either. It’s one thing for reporters to omit information; it is something else entirely to purposefully mislead readers.
There are also certain implications in the Journal’s story that cast Jobs in an unflattering light.
William Hawkins, a doctor specializing in pancreatic and gastrointestinal surgery at Washington University in St. Louis, Mo., said that the type of slow-growing pancreatic tumor Mr. Jobs had will commonly metastasize in another organ during a patient’s lifetime, and that the organ is usually the liver. “All total, 75% of patients are going to have the disease spread over the course of their life,” said Dr. Hawkins, who has not treated Mr. Jobs.
Getting a liver transplant to treat a metastasized neuroendocrine tumor is controversial because livers are scarce and the surgery’s efficacy as a cure hasn’t been proved, Dr. Hawkins added. He said that patients whose tumors have metastasized can live for as many as 10 years without any treatment so it is hard to determine how successful a transplant has been in curing the disease.
This is ugly business. They’re quoting a doctor who specializes in pancreatic and gastrointestinal surgery as saying (1) that it’s common for someone who had the cancer Jobs had to subsequently get cancer in their liver; (2) that liver transplants are not proven to help in such cases; and (3) obtaining a liver transplant in such cases is therefore controversial because it’s taking a liver that could otherwise have been put to better use by someone with some other type of liver ailment. There is no other way to read this than as an implication that Steve Jobs may have gotten a liver that should have gone to someone else. Keep in mind that this entire ugly implication is not stated as fact and is attributed as speculation from a doctor who admittedly has not treated Steve Jobs. But the fact that it is in the story at all makes me question whether any of the information in the story came with Steve Jobs’s permission, tacit or otherwise.
Theory 3: That a member of Apple’s board of directors leaked the information to the Journal without Jobs’s permission or knowledge, or perhaps, if the matter of public disclosure had been posed to and dismissed by Jobs at a board meeting, expressly against Jobs’s wishes. The scenario I am imagining here is that Jobs does not wish to reveal anything regarding his medical situation, but that a member (or contingent) of Apple’s board believes it is in the company’s interest to release the basic gist of the story, regardless of Jobs’s wishes. This scenario would explain the timing, the certainty, and perhaps even the lack of sourcing. (Although if this scenario is the case, certainly Jobs himself must suspect the source of the leak is from the board.)
Note also that some portions of Kane and Lublin’s WSJ report must have been sourced from someone on, or very close to, Apple’s board of directors:
When he does return, Mr. Jobs may be encouraged by his physicians to initially “work part-time for a month or two,” a person familiar with the thinking at Apple said. That may lead Tim Cook, Apple’s chief operating officer, to take “a more encompassing role,” this person said. The person added that Mr. Cook may be appointed to Apple’s board in the not-too-distant future. […]
At least some Apple directors were aware of the CEO’s surgery. As part of an agreement with Mr. Jobs in place before he went on leave, some board members have been briefed weekly on the CEO’s condition by his physician.
Who else other than a source on Apple’s board would know that Tim Cook may soon join the board, or that some board members were briefed weekly?3
This third scenario is my best guess as to the Journal’s source. It sounds sensational to speculate that there is conflict in this regard between Jobs and at least some contingent of Apple’s board of directors, but sensational or not, it makes more sense to me than any other scenario.
It also fits with my belief that Steve Jobs does not want to disclose anything about his health whatsoever.
As usual, I’m linking to a Google redirection to the WSJ story. If I link directly to the WSJ web site, only paid WSJ subscribers will be able to read the story. The WSJ allows referrals from Google to see full article content. ↩
Apple board member and Jobs confidant Al Gore is from Tennessee. But his home is in Nashville, not Memphis, so I can’t think of any reason Gore would have played a role in Jobs’s decision to go there. ↩
In theory the Journal’s source could be Tim Cook, but that goes against everything I have ever heard about Cook. I believe him to be loyal, honest, and to have deservedly earned Steve Jobs’s full trust. I truly believe that Cook would much prefer to continue in his current role in an Apple with Jobs as CEO than to be CEO of a Jobs-less Apple. Plus, Cook doesn’t need to angle through the press for anything. If Jobs steps down as CEO any time in the foreseeable future, the CEO job goes to Cook. No one whose opinion I value doubts this. It’s simply a question of whether Cook runs operations as “COO” with Steve Jobs overseeing product development, or as “CEO” without Steve Jobs overseeing product development. ↩
JavaOne is an enormous conference. Apple reported 5,200 WWDC attendees this year, and, to me, it once again felt more crowded than ever before. Sun reported three times as many attendees for JavaOne. Comparing any two conferences, especially long-standing ones such as JavaOne and WWDC, is apples-to-oranges, but there’s no denying that JavaOne has been at least as big a deal for Sun’s developer community as WWDC has been for Apple’s.
But now that Sun is in the midst of being folded into Oracle, it’s an open question as to whether there will even be another JavaOne. Even if there is another, it will surely be different, coming as it must in a future where Sun is a subsidiary of Oracle rather than a standalone industry titan. (As a complete outsider to the Sun and Java communities, I found Tim Bray’s elegiac JavaOne coverage to be compelling.)
To crudely paraphrase Dylan, a conference not busy being born is busy dying. WWDC is busy being born. The gestalt of the conference, and of Apple’s developer community, is very much in flux. Not just changing but growing. Between the Newton and iPhone eras, WWDC was effectively a Mac developer conference. That’s no longer the case, and with each passing year there’s a palpable difference to the vibe. (And it’s not just because of the iPhone, either. There are now a series of good sessions each year for web developers targeting WebKit.)
Two years ago, on the cusp of the iPhone’s release, was the last of the mostly-all-Mac WWDCs. The vibe that year boiled down to “I hope they let us write native apps for this thing.”
Both this year and last, there have been single sessions whose titles epitomized that year’s conference. Last year, the first year with an iPhone development track, that session was titled “Intro to Mac OS X”. It’s hard to imagine such a session title even one year earlier at WWDC, but I walked by that session last year just to see how crowded it was, and the line to get in ran out the door and down the hall all the way to the escalators. They had to turn people away. (Apple replayed the session on video later in the week and the replay filled to capacity, too.)
This year, the emblematic session was titled “Mac Programming for iPhone Developers”. I’m not even sure what to say about that, other than to confirm that anecdotal evidence suggests that new-to-Apple iPhone developers are indeed very much interested in developing for the Mac now, too.
On the whole, there was a palpable sense that the iPhone is a peer to the Mac in Apple’s eyes. This isn’t about counting how many sessions were devoted to each. Nor is it an indication that the Mac as a platform is slowing. Quite the opposite in fact — Apple is selling more Macs than ever, and, knock on wood, there’s a strong consensus amongst developers that Snow Leopard is going to be the best release of Mac OS X yet. It’s simply that for however fast the Mac is growing, the iPhone is growing far faster.
But the two platforms are symbiotically intertwined. The Monday schedule at WWDC is static. In the morning comes the keynote, which the press attends and where all public announcements are made. After lunch, though, there comes what is effectively a second keynote, this time with material aimed squarely at developers. A technical keynote, as compared to the morning’s marketing keynote, if you will. This technical keynote has for as long as I can remember been titled “Mac OS X State of the Union”. This year the title changed to “Core OS State of the Union”.
Hence the symbiosis: Apple now has two full-fledged developer platforms, Mac OS X and iPhone OS, derived from one core system. Neither felt more important than the other this year at WWDC, which is remarkable considering that one of them hadn’t even shipped two years ago.
But look at their vectors — their relative rates of growth — and ponder how much longer until WWDC begins to feel like an iPhone developer conference with a Mac developer track. My answer: next year. In other words, I think it will have taken just three years for the iPhone to supplant the Mac as Apple’s primary platform. By 2011 it will be obvious.
It’s simply a matter of users. During Phil Schiller’s keynote, he showed a graph of the “OS X” user base over time, with steady growth over the first part of this decade followed by a sharp jump from 25 to 75 million over the past two years. This figure was widely mis-cited, however, as showing growth in “Mac OS X” users. It did not. The graph said “OS X”, not “Mac OS X”, and what Apple meant to show were the combined number of users of Mac OS X and iPhone OS. It was a very misleading and poorly-designed chart.
The other relevant number from the keynote: 40 million total iPhones and iPod Touches sold to date. Clearly that’s not quite the same thing as 40 million iPhone OS users, given that some of us have already bought several devices, but it’s in the ballpark. So, as of last week, Apple estimates that there are about the same number of iPhone OS users as Mac OS X users.
Now consider what those numbers will look like a year from now, 12 months after the iPhone’s entry price dropped to $99.
]]>Everything I wrote about last month in “The Next iPhone” still stands. I expect Apple to announce updated iPhones with significantly faster processors, twice the RAM, and twice the storage. I expected prices to remain the same as the current lineup: $199/299 for 16/32 GB, respectively. The video camera is going to be a major selling point.
One additional tidbit I’ve heard is the new hardware’s code name: iPhone 3GS. I’m not certain that’s what it’ll be officially named, but my hunch is yes. I have no idea what the S stands for.1
The other new tidbit is battery life: 15-20 percent longer than the iPhone 3G.
As for form factor, I believe the 3GS will have the same or very similar dimensions as the 3G; the screen size is unchanged and existing cases might fit the 3GS. I assume that the new models must look different — newer, cooler — in some way, but I don’t know how.
There are pervasive rumors that Apple is also set to announce lower price points for the iPhone. The Financial Times, citing anonymous sources “familiar with the initiative”, reported it as fact.
I believe this is true, and the new price will be $99. But since I expect the new top-of-the-line iPhone 3GS to start at $199, that means the $99 iPhone must be something else. I see two possibilities: (a) a new device, something that is to the iPhone what the iPod Mini was to the original iPod; or (b) the existing 8 GB iPhone 3G, unchanged but reduced in price.
I would wager heavily on (b) — that the new iPhone 3GS models will not replace the 3G, but rather assume the flagship position while the year-old 3G slides down to the second spot in the product lineup. I believe Apple will eventually create an iPhone Mini or Nano or Junior — something that is smaller and thinner, in an array of colors but with fewer features and lower tech specs, at lower prices. And when they do, they will promote it heavily in a major play for raw mobile phone market share.
I don’t think that time is now, though, which is why I believe the imminent $99 iPhone will simply be the existing 3G at a reduced price. I’m not even sure this $99 iPhone will be announced at WWDC — Apple may well wait until the new iPhones are available for sale to announce it. In fact, if I’m right that the $99 iPhone will simply be a reduced-price 3G, I wouldn’t be surprised if it were something Apple sold only through its own stores, and perhaps only for a limited time until their stock of old 3G models is gone.
It’s no secret that iPhone OS 3.0 supports tethering: sharing the phone’s 3G internet connection with your computer. What we don’t know yet is how this will work with Apple’s various carrier partners around the world. It’d be nice if it just worked, with no additional charge over the current data plan. But “it’d be nice” seldom happens with phone carriers. So I expect we’ll be charged for this feature; the question is how much.
At a fair price and assuming the feature works well, iPhone tethering could obviate the need for something like Verizon’s MiFi. I look forward to never paying for hotel or airport Wi-Fi service again.
The big question with Snow Leopard isn’t with regard to technical details, but its marketing. Starting with version 10.2, previous major updates to Mac OS X have sold for $129, and were marketed almost entirely based on their new features. Apple has explicitly made clear that with Snow Leopard its focus was not on adding new features but rather on improving and optimizing existing ones — shoring up the foundation of the core OS shared by the Mac, iPhone, Apple TV, and future products to be named later. I think this was a great idea. OS X is here for the long haul — it is the foundation of Apple’s entire business for the foreseeable future.
But how do they sell Mac OS X 10.6 to consumers if it doesn’t bring major new features? Here are the options I see:
Sell it for $129, just like previous major updates. Advertise it as faster and better. If it doesn’t sell as well as 10.5 Leopard did, well, so what? Slow uptake would be an irritation for developers who want to ship software that depends on 10.6-specific APIs, but it wouldn’t be the end of the world. And who knows? Apple has never tried selling a full-priced OS update based on something other than new features — it might sell as well or better than 10.5 did. Maybe it’s not true that people only pay for features upgrades.
Sell it for a lower price, say $59.
Sell it for a nominal price, say $19. I think free is out of the question, if only because of Apple’s interpretation of U.S. accounting regulations. They give iPhone owners free OS updates because they use subscription-based accounting for iPhones. They charge iPod Touch owners for the same OS updates, because iPod Touches aren’t accounted for on a subscription basis. The Mac is like the iPod Touch in this regard, so I think a free Snow Leopard isn’t possible.
The risk with options 2 and 3 is that it might make it more difficult for Apple to go back to charging $129 for 10.7 and beyond. But Apple is not Microsoft. OS upgrade revenue is a nice extra for Apple, not a core part of its business.
The wildcard with Snow Leopard would be if Apple were set to unveil some sort of heretofore secret new features, features which they could then use as the basis for an advertising campaign and the regular $129 price. But from everything I’ve heard, Snow Leopard development is winding down — they’re tying off loose ends and fixing bugs.
I have no idea how Apple is going to play this.
The other X-factor is “Marble”, the rumored redesign of the entire OS’s visual appearance. Could that be the secret Snow Leopard “feature”? Six months ago that’s what I was expecting: that from an engineering point of view, Snow Leopard’s changes would be low-level, but that by making everything look all-new, Apple would have an obvious way to sell it to consumers as something worth paying for. If it looks new it is new, from a normal person’s perspective.
But while I am convinced that “Marble” is a real design project at Apple, I no longer believe it is slated for Snow Leopard. A new visual appearance isn’t something Apple can spring on third-party developers at the last moment. If they plan to ship Snow Leopard soon — say, by the end of August — that just isn’t enough time to allow developers to update their software to look good under a new UI theme. (There’s also the problem of creating software that looks good under both the new and old themes.)
So my hunch is no Marble for Snow Leopard — that it’s now a 10.7 thing. But I’d never bet too much money on the side of Apple accommodating the needs of third-party developers.
I’m completely convinced that the tablet is real. But I am almost just as convinced that it is not ready to be announced. Patience on this one.
]]>