A few years ago I worked as a journalist, and one of the major events at the time was news photographers hating the fact that newspapers were sending out normal reporters with DSLRs and telling them to take 200+ shots. Most of the time, they took a usable photograph. The pro news photographers said, 'But you can't expect an untrained person to take good photographs!' And they insisted that the papers stop sending out camera-armed news reporters.
The thing with that, though, was that if you John Random Reporter couldn't take pictures of near-equivalent quality to a John Pro Photographer, the papers would stop doing it. But they didn't. If the photographers' point was true, they had nothing to worry about. But they knew they did indeed have something to worry about. The truth was that the amateurs could come close enough to equalling the pros that the trade off versus cost savings was worth it.
There is a parallel here with closed versus open systems. We howl, 'You can't do that!! Closed systems canot possibly equal the innovation and development of open!!' And if that's the case, we have nothing to worry about. Quite possibly, though, that is not the case. The insistence on closed that seems so anathema to much of the history of software development may in fact be a good thing for the end user, and our howls of outrage nothing more than being called on something that is no longer true.
That sense of threat would at least explain the inordinate number of HN stories on this topic.
The problem with this is that the erosion of quality is not necessarily noticed immediately, but the slow increase of dissatisfaction builds until people finally reach the quitting point.
There's many instances of media where I look at older versions of the product and think, "man, why is this quality absent from their product today?". I didn't consciously notice it when the snowball was still near the top of the mountain. But eventually the snowball got big enough for me to bail.
The insistence on closed that seems so anathema to much
of the history of software development may in fact be a
good thing for the end user
Users are happy right now, but the time line of returns is significant. People will be unhappy about losing their music, or when they can't get important apps upgraded.
Closed systems generally aim to give you a capability quickly, but lock you in as they do. Open systems are often a dog to get working, but once you do you find the capability continues to pay dividends.
- Visual basic lets you create apps quickly but there's a lot of things you can't do, and your platform might be taken away from you.
- Microsoft word allows anyone to create small, well-formatted document with low training. But there's tooling lock-in, it's unwieldy to have many people work on documents, it's hard to transform your data.
- Iphone lets you get easy access to music and apps. But they won't transfer forever; long-term upgrade options are even more complicated than in consulting software because Apple would need to participate in maintenance.
Something we've seen with open platforms is that they move slowly but rarely lose ground. The PC architecture and unix are examples.
I know it's not your point, but something you said got me thinking about something else.
"Closed systems canot possibly equal the innovation and development of open!!'"
I always look at the internet as proof that an open system that was successful because it was open. The same with email. Both of these systems was more successful than anything Apple could every do.
In the world of closed v.s. open, closed is generations behind in the innovation and success department.
Interesting perspective because it equates devs with musicians, which while not an intuitive comparison might be increasingly accurate.
If it is, the future is not promising. Musicians have been getting screwed for years by record labels. They put up with it because their primary goal was to create, and find an audience. Being treated like a commodity by the record labels was aggravating and dehumanizing but didn't stop either music production or the practices of the labels.
Maybe all of us 'rockstar' developers should be careful what we wish for.
Ah, but musicians got screwed by Apple, too! (I might add that the record label bogeyman is clearly in no danger of disappearing from the collective consciousness of Hacker News.)
Here's the thing: Apple is a platform company, and in essence, it's been in the business of screwing those that are hostage to its platform at least since its renaissance. Apple doesn't want those in its ecosystem to make much money, because it wants you to give it your money.
That's why it said "Rip. Mix. Burn." with respect to musicians' work back in 2001 (to much cheering and adulation from developers): they were quite happy for you to get all your music for free (at the expense of the artists and labels), and instead allocate your disposable income to their hardware devices. When they opened iTunes, they added insult to injury by not allowing musicians to control how their music gets packaged and priced. I don't remember anyone complaining about the Apple's hard-driving tactics then.
And lo, now they're treating third-party developers with the same contempt they previously reserved for musicians -- and suddenly the Hacker Community is up in arms. Plus ca change...
> Maybe all of us 'rockstar' developers should be careful what we wish for.
It's what you wished for ten years ago that put you in the quandary you now find yourselves in. Apple's stranglehold on music is what gave it the wherewithal to extend into other areas.
Hacker News, you've just discovered what it feels like when someone's got you by the balls.
Boring. It's actually a pretty good analogy though.
Musician: hai! I play bongo music. Can I be signed to your label?
Label: uh no, we're a rock label. You must use much guitars.
Musician: This is outrageous! I must get the online world
to feel outrage and boycot you.
Can we stop all the whining and reactionary moral outrage on hackernews yet? Please? :(
If you don't like it, go make your own iPhone/iPad instead of incessantly whining like some teenager that isn't allowed out.
We will stop being outraged as soon as outrageous things stop happening.
In this case Apple is the music label, the music shop and the people that make the CD player. And that's the problem. If there were multiple app stores for the iPhone then nobody would care if Apple chose to filter the apps in their store.
I've been on HN for a long while now, so I believe I'm allowed to say this: I hate the idea of HN turning into Reddit. I hate 'news' stories about how we should all be outraged and boycot something. It's a ton of sheep following some ill advised, likely false rumor half the time. It's just kids in the playground trying to exercise mob rule.
There was a news story, saying how Apple have changed their wording to disallow non-approved languages for developing apps. Great. That's news. But 100+ follow up 'opinion pieces' on it? srsly? Do we need all that crap? 10 out of the top 22 stories on HN are about this one item!
The biggest mistake Apple has made IMHO has been opening the app store to all developers. They should have carefully selected chosen, quality partners, who would agree to play by Apples rules.
At the end of the day though, the general public doesn't care one bit how Apple "treat" developers, so it's all fairly moot.
If you take some principled stand by not making another worms game because you can't write it in clojure, you can be sure as hell someone else will just get on with it and write it in whatever Apple want.
At the end of the day though, the general public doesn't care one bit how Apple "treat" developers, so it's all fairly moot.
I keep hearing similar logic from lots of people - but surely you would agree that the general public cares about what cool apps they can run on their iPhone vs. their neighbor's Android? Up until now most devs have grit their teeth and tolerated the App store policies since they were outweighed by Apple's superior market size, UX, and even dev tools (Xcode, instruments, the simulator, and the SDK itself are all probably more well-thought out than their Android counterparts). But if you push them hard enough, they will move, and not just the ones with free software moral outrage.
Lots of other people have compared Apple's policies favorably with the policies of the video game console manufacturers. I invite those people to look at the history of what happened in the mid '90s in the transition from the Genesis/SNES era to the PlayStation/N64 era.
Apple's decision was undoubtedly not arbitrarily made. It was not an accidental combination of rules that produced something developers find distasteful; it was very intentional and deliberate.
I agree with axod: the "general public" doesn't care about the development environment for their Apple products. They just want things to work. If this rule results in a worse experience for consumers, Apple might have to repeal it; if not, it will probably stand.
If you really want a better situation for developers, stop with the boycots and "mob rule," as axod called it. Spend your time helping to increase the quality of an alternative platform that seems more developer friendly.
(P.S. 9 out of thirty stories on HN's main page are Apple related -- wtf.)
The thing is, a lot of people see a huge potential in this platform, and they're sure it could be ten times better if only Apple decided to be a bit less closed.
Or you can go make an app for the android. I have a few phonegap applications I've been making for different projects. When I first started everyone had iPhones, now most of the clients have moved to droids (Verizon far outperforms ATT in NYC.) and the apps still work just fine.
In conjecture, making apps for the android is probably the biggest way you can make a difference, much more then convincing a few people not to drop a few hundred dollars over the next few months. Make a few big sellers on the Android market and you'll encourage app development and make some money.
This is a horrible analogy. When you produce music it doesn't have to hook into an external API. Can badly produced music crash a device (aside from the user's ears)? No.
No, it is a great analogy. Think of it this way, the record labels do what Apple does with it's review process -- ensure that 'quality' music is produced and distributed to listeners. But record labels do not limit what instruments can be used to produce that music.
If Apple allows C, and they do, the choice of tool doesn't affect whether or not the device will crash.
A better analogy, since even non-musicians can hear the difference, would be Apple banning from iTunes any General Midi 1.0 song covers recorded using Sound Blaster cards with FM/OPL-3 chips, but still allowing music from Kraftwerk to Imogen Heap.
(In that sense, both Ableton and GarageBand could be considered construction kits, so perhaps a better analogy would be if iTunes banned sequenced music, only allowing music musicians personally play?)
Why not judge the applications on the difference (i.e. the end result), then, rather than the mechanism?
We're not just talking about Adobe Flash for iPhone here. We're talking about ruling out any innovation in targeting the platform, even innovation specifically targeted at the iPhone and with no limitations or sameness involved.
The analogy is broken. Humans don't interact with music in the same interactive way that they do with software. Music does not execute on your computer (except for DRM stuff, perhaps).
I don't think you'll ever hear someone say, "This music is full of bugs! It keeps crashing on me."
The analogy isn't broken because record labels and Apple both have a "review process". But record labels don't limit what instruments you can use. What Apple has done will not reduce the number of bugs or prevent crashing.
Analogies are useless for debate, no matter how good they are. Anyone who doesn't agree just provides a different analogy that supports their point better, and then the argument shifts to arguing which analogy is better!
Wrong analogy. It's more like a distributer (not label) telling its affiliates that for their CDs to be shipped, the songs on them must now have been originally written only in Mixolydian mode in the key of G with a 4/4 time signature. Anything else is not allowed, especially something that doesn't even use western musical scales or tuning.
What apps are worth buying anyway? I spent the first day with my ipad looking for an app that reads pdf for christsake. The entire platform seems to be just big media & games.
The thing with that, though, was that if you John Random Reporter couldn't take pictures of near-equivalent quality to a John Pro Photographer, the papers would stop doing it. But they didn't. If the photographers' point was true, they had nothing to worry about. But they knew they did indeed have something to worry about. The truth was that the amateurs could come close enough to equalling the pros that the trade off versus cost savings was worth it.
There is a parallel here with closed versus open systems. We howl, 'You can't do that!! Closed systems canot possibly equal the innovation and development of open!!' And if that's the case, we have nothing to worry about. Quite possibly, though, that is not the case. The insistence on closed that seems so anathema to much of the history of software development may in fact be a good thing for the end user, and our howls of outrage nothing more than being called on something that is no longer true.
That sense of threat would at least explain the inordinate number of HN stories on this topic.