Everything you read in newspapers is absolutely true, except for that rare story of which you happen to have first-hand knowledge. ~Erwin Knoll

I ended up spending a fair amount of time disproving an obviously wrong newspaper story last night. It didn’t work.

In college, I was a member of the Stanford Band, a group I keep up with via Facebook and alumni e-mails. They were featured in a Miami Herald front page story this weekend, about their antics and their upcoming performance at the Orange Bowl pregame.

Imagine my surprise when the San Francisco Chronicle reported that the Band was banned from performing at halftime. Surprised, because the story is totally wrong.

The Chron story sources an MSNBC story, which itself cites no sources, and whose URL suggests it is a local affil item submitted to MSNBC. The MSNBC story’s facts are all from the Miami Herald write, and is likely its only source, and uncredited at that. Here’s the last two grafs of the Herald write:

South Florida is not exactly Arkansas, but cautious Orange Bowl organizers have reduced the opportunity for indignity by keeping both college bands off the field at halftime; they’ll be restricted to brief, six-minute pregame shows.

Stanford Band bosses are keeping mum about their plans, saying only that the show is titled Recent Events in the Pro Sports World in Miami. Look out, LeBron.

This omits a crucial fact — Orange Bowl halftimes are always gala affairs that do not involve the marching bands — but this is written around in an amusing tone that’s consistent with the rest of the article.

The MSNBC affil didn’t pick up that fact, or on the light tone, and took those last grafs for their lead:

Fearing an en masse pants drop, or just wanting to protect their newest celeb athlete, LeBron James, from OJ Simpson-style mockery, the Orange Bowl administrators have decided to keep the bawdy Stanford Band from performing at halftime.

MSNBC picked a few highlights of the Band’s antics for the body of their article, then returned to the “banning” in their last grafs:

Denying the Stanford Band a stage also denies Virginia Tech one. The Orange Bowl will only allow the teams’ bands to perform in six-minute bursts before kickoff.

The Band’s show is entitled “Recent Events in the Pro Sports World in Miami.”

Whose talents could possibly be targeted, er, featured?

Using the MSNBC write as its only source – and with apparently no vetting of the facts via a local call to Stanford’s athletics department – the Chronicle turns the lightweight kicker from the Herald into a hard lead:

Orange Bowl administrators, determined to make tonight’s matchup between No. 5 Stanford and No. 12 Virginia Tech less entertaining, have decided to bar Stanford’s irreverent band from performing at halftime.

The move comes after the band announced its show was entitled: “Recent Events in the Pro Sports World in Miami.”

This is where I got involved. Hopping into the article’s comments section, I posted a series of followups, determined to prove the article false. The last comment I posted linked to four sources that could completely dispel the story:

I also e-mailed the writer of the article. I would have thought this would be enough to get the article – demonstrably and totally wrong – retracted.

Instead, it’s still on SFGate’s front page the next morning:

Obviously, this has hit a nerve with me. I can’t help it: I used to be an editor. When ESPN ScoreCenter sent me a push notification of the game’s final score, including the text “A. Luck(STAN) 4TD, 0INT”, my first thought was “Bullshit, he threw a pick in the second quarter.” Loyalties be damned, A is still A.

To see a major newspaper so sloppy and so obviously wrong is shameful. When I was writing and editing at CNN, if I had ever used a single source, which cited none of its own sources, with no vetting and no common sense fact-checking, I’d have been busted back to separating carbons in the printer room within a week.

Frankly, I’m going to get a good chuckle the next time one of the Chron’s 27 liberal columnists complains about obvious falsehoods on Fox News. It should also rankle that Wikipedia gets this more right than the Chron does. From a overnight edit to the Stanford Band article:

Despite Twitter rumors to the contrary, the band was not banned from performing during the 2011 Orange Bowl halftime. The Orange Bowl traditionally has major-label recording artists perform the halftime show, not school marching bands (The Goo Goo Dolls performed the 2011 show). They did, however perform during pregame, which was briefly shown on the game’s national broadcast. The theme of that show was “Recent Events in the Pro Sports World in Miami.”

Yesterday was a really rough day for me in terms of getting things straight. I also, perhaps foolishly, hopped into discussions of a Detroit Free Press article discussing the possibility that Stanford coach Jim Harbaugh could be the one to turn around the University of Michigan’s slumping football program. There’s a lot of enthusiasm for that here in Michigan, and I’ve been trying to throw cold water on it. Sure, I’m motivated by the implicit slight to Stanford. But moreover, it’s not a given that Harbaugh would want to give up a top-5 program that he’s built in order to start over with a reclamation project, one that he pointedly insulted a few years ago. It would, you’d think, at least take a dump truck of money. Moreover, a number of NFL teams are openly courting Harbaugh. I posted comments with links to articles indicating the 49ers, Broncos, and Panthers were openly pursuing him, along with a nice New York Times profile that covered Harbaugh’s options.

The result? A lot of people calling me various names, and one poster in particular who insisted repeatedly that it didn’t matter because Michigan had already hired Harbaugh a month ago. Now how does this even pass Occam’s Razor? Why would the NFL teams waste time and money, and a chance to land coaches who are actually available, if U-M had already secured Harbaugh’s services, or even thought they had? Why would anyone even be talking about it if it were a done deal? It can’t be, not yet anyways, and yet this guy stuck to his guns.

And yet, how is that any different from the Chron? There’s no penalty to being obviously wrong. When the facts aren’t on your side, just yell louder. The Big Lie works, in part because people believe what they want to believe. The Chron’s totally wrong article has been shared to Facebook nearly 1,700 times as of this writing.

We all know the internet is a breeding ground for ignorance, that you can find seemingly reputable sources for whatever stupid nonsense you care to believe (Obama’s not really American, 9/11 was an inside job, the CIA created AIDS to kill black people, etc.), but it’s still ghastly to see it in action.

My local paper recently declared it’s getting tough with trolls in its forums, and while I wish them the best, I wonder if it isn’t better in the long run to just ditch user comments altogether. I find I enjoy the consistent voice of an author – Daring Fireball is the obvious example of this in the Mac/iOS world – whereas I rarely find anything of value in feedback forums, just a mudslinging scrum among various partisans.

Comments should allow for readers to communicate back to publishers, and could provide a valuable means correcting bad information. And as professionals, publishers should want to be right: it’s the only thing that distinguishes them from any random Joe with a website.

But that’s where we started. I tried correcting them. It didn’t work. And the Chron is still happily collecting hits on an article that’s demonstrably and totally wrong.

Like a lot of old programmers — “when I was your age, we used teletypes, and line numbers, and couldn’t rely on the backspace key” and so on — I sometimes wonder how different it is growing up as a young computer programmer today. Back in the 80′s we had BBSs, but no public internet… a smattering of computer books, but no O’Reilly… and computer science as an academic discipline, but further removed from what you’d actually do with what you’d learned.

Developers my age grew up on some kind of included programming environment. Prior to the Mac, every computer came with some kind of BASIC, none of which had much to do with each other beyond PRINT, GOTO, and maybe GOSUB. After about the mid-80′s, programming became more specialized, and “real” developers would get software development kits to write “real” applications, usually in some variant of C or another curly-brace language (C++, C#, Java, etc.).

But it’s not like most people start with the formal tools and the hard stuff, right? In the 80′s and 90′s, there were clearly a lot of young people who picked up programming by way of HyperCard and other scripting environments. But those have largely disappeared too.

So what do young people use? When I was editing for O’Reilly’s ONJava website, our annual poll of readers revealed that our under-18 readership was effectively zero, which meant that young people either weren’t reading our site, or weren’t programming in Java. There has to be some Java programming going on at that age — it is the language for the Advanced Placement curriculum in American high schools, after all — but there’s not a lot of other evidence of widespread Java coding by the pre-collegiate set.

I’ve long assumed that where young people really get their start today is in the most interesting and most complete programming environment provided on every desktop computer: the web browser. I don’t want to come off like a JavaScript fanboy — my feelings about it are deeply mixed — but the fact remains that it is freely and widely available, and delivers interesting results quickly. Whereas 80′s kids would write little graphics programs in Applesoft BASIC or the obligatory 10 PRINT "CHRIS IS GREAT" 20 GOTO 10, these same kinds of early programming experiences are probably now being performed with the <canvas> tag and Document.write(), respectively. In fact, the formal division of DOM, CSS, and JavaScript may lead the young programmer to a model-view-controller mindset a lot sooner than was practical in your local flavor of BASIC.

The other difference today is that developers are much better connected, thanks to the internet. We didn’t used to have that, so the programmers you knew were generally the ones you went to school with. I was lucky in this respect in that the guys in the class above me were a) super smart, and b) very willing to share. So, 25 years later, this will have to do as a belated thank you to Jeff Dauber, Dean Drako, Drew Shell, Ed Anderson, Jeff Sorenson, and the rest of the team.

Did I say “team”? Yeah, this is the other thing we used to do. We had a formal computer club as an activity, and we participated in two forms of programming contests. The first is the American Computer Science League — which I’m releived to see still exists — which coordinated a nation-wide high school computer science discovery and competition program, based on written exams and proctored programming contests. The cirriculum has surely changed, but at least in the 80′s, it was heavily math-based, and required us to learn non-obvious topics like LISP programming and hexadecimal arithmetic, both of which served me well later on.

Our school also participated in a monthly series of programming contests with other schools in the suburban Detroit area. Basically it worked like this: each team would bring one Apple II and four team members and be assigned to a classroom. At the start of the competition, each team would be given 2-4 programming assignments, with some sample data and correct output. We’d then be on the clock to figure out the problems and write up programs, which would then be submitted on floppy to the teachers running the contest. Each finished program scored 100 points, minus 10 points for every submission that failed with the secret test data, and minus 1 point for every 10 minutes that elapsed.

I have no idea if young people still do this kind of thing, but it was awesome. It was social, it was practical, it was competitive… and it ended with pizza from Hungry Howie’s, so that’s always a win.

Maybe we don’t need these kinds of experiences for young programmers today. Maybe a contrived contest is irrelevant when a young person can compete with the rest of the world by writing an app and putting it on the App Store, or by putting up a web page with all manner of JavaScript trickery and bling. Still, it’s a danger to get too tied to the concretes of today, the specifics of CSS animations and App Store code-signing misery. Early academic exercises like earning to count in hex, even if it’s to score points on a quiz, will likely pay off later.

Yesterday, I took my 5-year-old daughter, Quinn, to the Beauty and the Beast sing-a-long event. Quick summary: would have worked better with more people (we only had about 20, and most were shy), but helped to be in front of some theatre girls who knew the songs by heart and were into it. Still, one of my favorite movies, one I’ve surely seen 20 or 30 times. But let’s get back to digital media…

The event was meant to promote Tuesday’s re-release of Beauty and the Beast on home video, this time in its first HD edition. I’ve already owned B&tB on VHS and DVD (the 2003 edition cleverly contained the “work in progress” film circuit version, the original version, and the IMAX re-release that added an unneeded song). So I found myself wondering if I would be buying this release. Probably not, since I don’t own a Blu-Ray player and now that we’re many years into the Blu-Ray era, I don’t see that changing anytime soon. We don’t do a lot of movie watching anymore, as most of what we watch is DVR’ed off the DirecTV, and I didn’t fall for the “PlayStation 3 as Blu-Ray trojan horse” due to the PS3′s absurd unaffordability. And I don’t feel like we’ve missed it.

Then I thought: “wait, Blu-Ray isn’t the only form of HD.” There’s also on-demand from DirecTV, and what about iTunes? A little search there shows that yes indeed, the B&tB platinum edition will also be available on iTunes: $14.99 for SD, $19.99 for HD.

Of course, these Disney classics are usually only available for a short time before they “go back in the vault”, to enhance demand for the next re-release. So if I felt I did need to grab an HD version before it went away, which would I get?

Thinking about it, I think I’m more likely to buy an AppleTV — or at least rig a Mac Mini to a TV — before I get a Blu-Ray player. As it is, I could play the HD .m4p on a bunch of the devices I currently own (computers, iPhone, iPad), and the only thing that’s missing is connectivity to the TV. In fact, various video out cables allow for iOS devices to serve as a sort of “poor man’s” first-gen AppleTV, depending on your available connections, how many videos you’ve loaded on your iPod, and your tolerance for SD. A Blu-Ray disc would be locked to the TV the player is connected to, and wouldn’t be rippable for the iDevices (though this particular bundle may come with a digital copy… haven’t checked).

Still, I’m surprised to find that I’ve blundered into exactly what Steve Jobs purportedly told a customer in one of those alleged off-the-cuff e-mails: Blu-Ray is coming up short, and will eventually be replaced by digital downloads, just as CD successors were beaten by downloads (anybody spun up an SACD lately?).

BTW, Apple’s resolute anti-Blu stance is made all the more interesting by the fact that Apple is a board member of the Blu-Ray Disc Association.

Another note about the AppleTV: teardowns and other spelunking reevel that the new device runs iOS and has 8GB of storage, which would be suitable for apps, should Apple ever choose to deliver a third-party SDK. Clearly the UI would be different — perhaps it exists not as an “AppKit” or “UIKit” but rather a “TVKit” atop Foundation and the rest of the usual Apple stack — but there would be all sorts of interesting opportunities.

One of the most obvious would be for all the existing iOS streaming media apps to connect to the TV. This includes the sports apps — everyone knows about the MLB app, but look further and you’ll find apps for major events like the PGA Championship and Ryder Cup also have their own apps with live video available via in-app purchase, DirecTV’s “NFL Sunday Ticket” streams to phones, etc. There are also specialized video apps for all manner of niches. For example, as an anime fan, I use Crunchyroll’s streaming app, and might someday sign up for Anime Network Mobile. I imagine every other little video fetish has its own streaming app, or soon will.

(By the way, none of these apps can use the standard def video out cables like Apple’s iPod or Videos apps can. When you connect the composite video cable and do [UIScreen screens], you only see one screen, so these streaming apps can’t access the video out and put their player UI over there. rdar://8063058 )

By Apple fiat, essentially all of these apps need to use HTTP Live Streaming, and an AppleTV that permitted third-party apps would presumably drive even more content providers to this standard. I had previously wondered aloud about doing an HTTP Live Streaming book, but if we get an AppleTV SDK, it would make perfect sense for the HLS material to become one or two chapters of a book on AppleTV programming, along the lines of “if you’re programming for this platform, you’re almost certainly going to be streaming video to it, so here’s how the client side works, and here’s how to set up your server.”

It’s easy enough to get hits with bad tech journalism: just rile the Apple fanboys. The Mobile Technology Weblog’s Microsoft Announces iPhone Killer deserves accolades for not involving any kind of actual announcement, nor in any way substantiating how its topic might be capable of “kill”ing the iPhone.

Android is a far more credible competitor to the iPhone, and as I said earlier, I’m interested to see if it can disprove some of Apple’s assertions about the way it conducts the iPhone ecosystem, such as the tightly-restricted review process or the prohibition on background apps, or if it will fail and thereby vindicate Apple. Still, whatever success Android might achieve, it’s hyperbole to posit it as an iPhone killer, at least at this stage.

Honestly, the two biggest threats I see to the iPhone come from the iPhone ecosystem itself.

In the worst case, one leads to mere tragedy, the other to catastrophe. Not that I’m predicting such a thing; I’m not a Cassandra (except when playing Soul Calibur, but that’s another story). But I do think these are issues that have the potential to cause great harm to Apple, its users, and its developers.

1. iPhone development is a bubble economy, already severely overinflated

Rilo Kiley, “The Execution of All Things“:
Soldiers come quickly, I feel the earth beneath my feet.
I’m feeling badly, it’s not an attempt at decency.

Surely only the most foolish and greedy developers at this point think they’re going to write a simple game and make a million dollars, like Steve Demeter, who pulled $250,000 in two months with the indie game Trism. The easy, early money has been made. Now there are 100,000 apps to compete with for attention, and only the top 2,000 have any significant usership.

But still, lots of developers are picking up Objective-C, learning from books like ours (thank you!), and putting their own time and money into writing their own indie apps. Even if they don’t expect to become iPhone millionaires, they’d at least like a shot at being, as Dan Grigsby aptly put it, warm, clothed, and fed with the proceeds of their iPhone work.

It’s possible the door has already largely closed to this too.

When I say that iPhone development is a bubble, I welcome you to interpret that in very literal economic terms. A developer who puts time and money into learning iPhone development does so in hopes of realizing a significant return.

And if you’re well off, well then I’m happy some for you.
But I’d rather not celebrate my defeat and humiliation here with you.

Personal case study: I put about two months of full time work into RoadTip… actually, three when you account for the month spent on the nightmare of implementing in-app purchase. That was time that I lived off a credit card, meaning I used a high-interest loan from Capital One to fund my development. I also put fixed costs, like artwork for the icon (from a former CNN colleague who used to work in the graphics department) and trademark registration on my card. So this is serious skin in the game.

After two weeks of sales, it is clear that I will never make back this investment. Not even close. I may never even make back the fixed costs, to say nothing of paying myself.

OK, there are reasons for this, not the least of which is the fact that there were no exit-finder apps when I started, and at least four others now (none of which seem to have bothered licensing their map data… would love to know how they’re not violating their providers’ terms of service). In the hit-driven App Store, you fall off your section’s “recently released” page after just a day or two, and unless you make the top 20 or have something else that makes you findable (a brand name, a well-travelled incoming link), you’re already dead.

Someone come quickly, this place was built for moving out.
Leave behind buildings, the city planners got mapped out.
Bring with you history, and make your hard earned feast.
Then we’ll go to Omaha to work and exploit the booming music scene, and humility.

If this is a hit-driven business, then the winners may be the ones who best understand marketing. And that’s the scenario by which we get lots of name-brand big-company apps, where there’s enough money to get the app in front of lots of people. The indie developer, who knows more about code than marketing, is at a severe disadvantage.

And if the risk of failure is not paying the mortgage, then it’s probably time for a lot of indies to bail out.

And this is still classic economics: too much money is in the iPhone market, chasing too little reward, and eventually there’ll be a pullback.

The question is if anyone will notice. Will the average user really miss 200 different Twitter clients or unit converters? Or is there some special, unique, topic-specific niche app that some tiny group of users would dearly love, and now will never get, because the developer who could write it is instead going to go take a contract to write the “American Idol Sing-A-Long Fun Kit”™ or god fucking knows what else?

Who knows? But much as I continue to think the world needs a touch-driven “IDE for podcasts”, something that might be extraordinary on a hypothetical OS X-powered tablet, I’m not going to risk any more of my own precious lucre developing such a thing. At this point, I expect my iPhone development to be largely for-hire works.

And we’ve been talking all night….

So that’s just sad, this one is dangerous:

2. Some of Apple’s iPhone development policies could violate anti-trust law

Anti-trust?! You should think I’m nuts. You’re probably thinking: Apple’s just a small player in a very competitive market, prone to lose their position at any time to strong competitors. You want to talk monopolies, let’s talk Microsoft.

No, I don’t want to talk monopolies. That’s the Sherman Act. I want to talk restraint of trade… the Clayton Act.

Consider this: the crux of the 90′s antitrust case against Microsoft — successfully prosecuted, if you’ll recall — was that Microsoft abused its dominant position by bundling its Internet Explorer web browser with Windows, to the disadvantage of Netscape Navigator, which had to be installed separately. Microsoft was branded as evil incarnate for the act of simply including a browser.

On the iPhone, Apple not only includes a browser, it prohibits developers from using any web-rendering technology other than WebKit.

Oh god come quickly, the execution of all things.
Let’s start with the bears and the air and mountains, rivers, and streams.
Then we’ll murder what matters to you and move on to your neighbors and kids.
Crush all hopes of happiness with disease ‘cause of what you did.

But that’s just the beginning. Consider some other technological and commercial restraints put on developers:

  • You may not use any interpreted language or a virtual machine in an app.
  • You must use Apple’s in-app purchase API, and pay Apple a 30% cut, for any post-sale commerce in your app.
  • Effective December 2009, streaming video to an iPhone can only be delivered with HTTP Live Streaming

There’s more, but that’s enough to get us started talking about tying, the practice of compelling a customer to purchase one product as a condition of buying another. The crux of my argument is: could this be applied to Apple’s App Store policies?

Maybe, if a court is sufficiently inventive. It’s been 18 years since I took Prof. Litman’s telecomm economics class in grad school, but he was particularly interested in antitrust law, and I recall the significant issues of that area of case law. In one case — and I’m sorry, I forget if it was FTC vs. Proctor & Gamble (the “Clorox Case”) or U.S. vs. Alcoa — the court was basically willing to invent a market within the defendant company’s operations, in order to claim that the market was closed to competition.

Let’s play with this line of reasoning. Can we imagine parties that might have a complaint against Apple for shutting off a market to them?

  • Sun (Java) and Adobe (Flash) for code-execution environments (i.e., interpreters and virtual machines)
  • PayPal and other payment processors for selling apps and handling in-app purchases
  • Adobe (Flash) and Microsoft (Silverlight) for video playback and streaming technologies
  • Opera and the Mozilla Foundation for web rendering technologies

All of these companies have services that they could sell to iPhone developers, but for the fact that Apple forbids their use on iPhone by fiat. Of course developers contractually agree to that, but they don’t really have a choice: it’s Apple’s way or the highway. And you may agree that it’s better that way; that’s entirely reasonable.

But if you successfully make the argument that things like in-app purchase processing or video streaming are competitive markets, then you might have a case that Apple’s App Store terms violate the Clayton Act.

Granted, I’m not a lawyer, and if it were such a slam dunk, then it’s fair to ask: why haven’t Adobe, Sun, PayPal and the rest sued on exactly this basis? Fair enough.

Still, if we woke up next week to an antitrust investigation of Apple’s App Store practices, it wouldn’t surprise me in the least.

And lastly, you’re all alone with nothing left but sleep.
But sleep never comes to you, it’s just the guilt and forever wakefulness of the weak.
It’s just you and me….

The execution of all things.
The execution of all things.
The execution of all things.

Sorry for the lack of updates. I’m traveling with family in San Diego, with the occasional futile one-day trip up to Disneyland (it may be the Happiest Place on Earth, but it’s no match for Autism Challenge Boy).

Anyways, had to get this off my chest. The Grand Rapids airport (GRR) has free wi-fi. Which is usually a good thing. They even have a special greeting page for iPhone users:

This page then changes to a “click to continue” page:

So you click the link to continue on to the original page you requested. Except that you end up back here:

Yep, the whole thing is a goddamn infinite loop of two advertising nag pages. And with no way to spoof your user-agent on the iPhone, there’s no way to get around it.

And it was this way when I departed from GRR for WWDC back in June.

And when we went down to Florida in February. On that occasion, I sent an e-mail to the airport asking them to fix it, and got a brush-off “yeah, yeah, you don’t understand our awesome technology, little boy” reply.

Anyways, the “FlyGRR” network is useless, and if you’ve had the misfortune to connect to it, there’s only one sensible course of action:

It’s annoying, but at least there’s no injury involved. That was reserved for our connection in Chicago. Ever heard those urban legends that escalators can rip kids’ Crocs, and sometimes some toes, right off their feet? Turns out it’s true. 4-year-old daughter Quinn was going up an escalator with my wife on the United concourse when her right Croc got caught. This is what it looked like after cleaning it (and her) up in the bathroom:

Notice that there’s a tear coming off one of the holes in the middle. Quinn describes the incident as “the escalator tried to take my Croc”. I still don’t know WTF happened, but I’m glad she’s not injured, and I guess I have to take the legend of Croc-eating escalators a little more seriously.

« Previous Page