The Forgotten Failure of Apple's PowerTalk

DECS writes "The series of articles Why Apple Will Change TV compared how Apple is poised for success in areas where Microsoft is currently failing. But circumstances are subject to change! Just over a decade ago, Apple began facing serious legacy problems with its platform, with many parallels to today's Microsoft. Examining Apple's dramatic fall provides a series of notable platform lessons that no company should ignore. A look back at the forgotten failure of Apple's PowerTalk: Apple vs. Microsoft in the Enterprise"

Comments

3 valuable lessons?

[pimpimpim]

The article mentions 3 valuable lessons:

1. Don't try to sell a futuristic product that doesn't quite work yet; instead, talk about it while selling as existing product that can compete in the current market.

2. Don't attempt to fire conceptual ideas at an imagined market; instead, craft finished products that solve real problems and can support a sustainable market.

3. Ship a functional product and then constantly refine it; Real world use and years of ongoing refinement create enormous value for a product.

Now, according to their lessons, google with all their betas must be a rightout disaster, shouldn't it?

Yeah but which tuner?

[Kadin2048]

What kind of TV tuner would you have them install?

Analog NTSC? Great, except that it'll stop working in a few years, and the quality is abysmal by modern standards.

ATSC? You get high-def, but you need an antenna, and even then you only get the big networks, which is a big step down to people used to 100+ channels of cable.

Clear QAM? It lets you use cable, so no antenna, but chances are you'll still only get the major networks, and it's arguably a greater pain in the ass than ATSC: many cable companies (Comcast, I'm looking at you) strip the metadata from their clear-QAM channels, making things like program guides really painful to use. And at the end of the day, you'll still be stuck with only the major broadcast networks, because those are the only ones that the cablecos are required to broadcast unencrypted. Everything else requires a proprietary converter box.

The solution would be CableCard, but there are still a lot of areas where you either can't get one, or are treated like shit and get a degraded level of service if you do. (And you pay several extra bucks for the privilege of renting the card.)

Given the state of the market right now, I wouldn't ship a computer with a TV tuner in it, either. If the FCC were to get its act together and really make CableCard the standard, and eliminate proprietary converter boxes, then I think you'd see an explosion in the types of set-top boxes and DVRs. I have no doubt Apple would be at the top of the list.

Same data, different conclusion

[Anonymous Coward]

As an email gateway developer, I worked with Exchange since it's inception and I attempted to use AOCE. When I compare that experience with what's going on now, I reach a very different conclusion.

Exchange started out life in the X.400 world. (If memory serves, Microsoft bought an X.400 product from someone else and GUIfied it.) This meant that even before the advent of the Internet Connector you could connect to Exchange using "standard" X.400 protocols. (I say "standard" because X.400 is so large and messy that pretty much everyone who implemented it was forced to deviate from the specifications in one way or another.) Not easy, but doable, and more to the point, doable from any platform able to deploy an OSI network stack. As Exchange shifted towards SMTP things improved to the point where Exchange was able to connect to existing facilities with little effort. (The article is wrong, BTW, in claiming that modem SMTP was around when Exchange first shipped. It was around but Microsoft chose to ignore it.)

AOCE, OTOH, only provided vast, arcane, incomplete and poorly documented Mac-specific API. The underlying protocols weren't documented at all. We tried hard to figure how to interface with this mess, even sitting down to discuss our issues with Apple folks at one point, but eventually gave up. And I'm talking a group of people who developed successful gateways to X.400-1984, X.400-1988, cc:Mail, Microsoft Mail, Novell MHS, and GroupWise among others. Either we are fools who got incredibly lucky several times over, or AOCE was an unmitigated disaster. And I don't think we were lucky fools.

But Apple learned their lesson. As the article points out, they now leverage open standards whenever possible. You can talk to a lot of Apple's new stuff over protocol. Sure, the APis are still there, and some of them are pretty nasty, but in a lot of cases you don't have to use them. Apple is also very active in various standards organizations (I wish they had had more success with Bonjour in the IETF, but that's a different matter).

Microsoft, OTOH, has utterly failed to learn anything from their experience with Exchange. They still roll their own whenever possible. They don't document the protocols they use, only the APIs, and of course those are only available on Windoze. I used to see lots of Microsoft people at standards meetings but not so many any more.

Of course things can change, but once things are headed in a particular direction they tend to stay on that course, even if it is a bad one. Everything I see about Microsoft says to me that they are on the wrong course and aren't doing anywhere near enough reinvention to correct it. The exact opposite appears to be the case with Apple.