3 ms·
So, I can understand why developers dislike and hackers despise the new 3.3.1 rules. What programmer, in their right mind, wants to have the language they deve
by ghshephard 17y ago
So, I can understand why developers dislike and hackers despise the new 3.3.1 rules. What programmer, in their right mind, wants to have the language they develop in dictated to them?
But, for just a moment, I'm hoping that some of you can appreciate how miserable an experience Apple users have had with the couple decades of various levels of cross-platform development that Microsoft has done.
At times, those applications have been _so_ bad as to be an advertisement for windows. I'm an Apple fanboy, and own three generations of Apple MBPs, three iPhones, and, of course, an iPad - but to this day, at work, I still keep a 2003 class Windows XP system with Microsoft Excel on it to get work done - The painful experience that is Office 2008, (and don't get me started on "NeoOffice") single handedly make me appreciate the fact that Apple is dictating that people write dedicated, high quality applications, directly for the iPhoneOS, rather than trying to do some crufty translation to that platform.
When I read Jobs's response, I could only imagine that he was having bad flashbacks to some of the x-platform disasters of years past.
I appreciate and respect that developers don't want to be told how to develop, but if the end result is that the few development shops out there capable of putting out a AAA title like Microsoft Excel, have to pony up a few more developer resources and put out a world class app directly for the iPhone OS, rather than just creating some half-baked x-platform experience, I'm in favor of 3.3.1.
- Silhouette 17y ago> I appreciate and respect that developers don't want to be told how to develop, but if the end result is that the few development shops out there capable of putting out a AAA title like Microsoft Excel, have to pony up a few more developer resources and put out a world class app directly for the iPhone OS, rather than just creating some half-baked x-platform experience, I'm in favor of 3.3.1. Well, OK, but the other possibility is that the executives at the few development shops out there capable of putting out a AAA title take one look at Apple's terms, observe that their entire investment could be arbitrarily yanked by another commercial organisation without compensation, kill the iPhone/iPad development before it starts, and target more open platforms that don't come with the same absurd levels of risk instead. In the long run, the developers will always win, because someone will always make a platform where good developers can write good software, and then people will buy that platform to get that software. On the other hand, no-one cares about the platform, even if it's Apple, once the initial "Oh, shiny!" moment wears off and you actually have to get stuff done.
- glhaynes 17y agoAren't there just as many, if not more, that will stay on iPhone (since it's where the money is) and use only approved tools? AAA-capable shops will build where the money is. There's been a LOT of controversy about Apple's terms in the last two years and I don't know of a single example of a AAA moving off the platform and onto a competing one. What's more likely is that they'll build a native iPhone version and use a cross-platform toolkit or HTML to build for the other mobile platforms.
- Silhouette 17y ago> Aren't there just as many, if not more, that will stay on iPhone [...] AAA-capable shops will build where the money is. Well, that's the question, isn't it? I would argue that the AAA shops will ultimately define where the money goes in the long term. Early adopters buy based on platform hype, but what really attracts users is good applications. > There's been a LOT of controversy about Apple's terms in the last two years and I don't know of a single example of a AAA moving off the platform and onto a competing one. I'm not sure any mobile applications have reached AAA level yet. It takes time, research and evolution to achieve that kind of status. But it also takes the right development team seizing the opportunity, and that in turn requires that team to be looking in the first place.
- wvenable 17y ago> an experience Apple users have had with the couple decades of various levels of cross-platform development that Microsoft has done. I'm not sure that proves your point here. Microsoft has had a Mac development team since the very first Macintosh. They write native software that is not a port of the Windows versions. In the past, IE for the Mac actually had more features (and was more standards compliant) than the Windows version. All this proves is that, yes, native apps can be crap. Which is exactly why this rule is entirely pointless. It's the not the development tool that matters, it's the developer. > single handedly make me appreciate the fact that Apple is dictating that people write dedicated, high quality applications, directly for the iPhoneOS, rather than trying to do some crufty translation to that platform. They're also eliminating any other tool or language which can also be written directly for the iPhone OS. Something like MonoTouch uses the iPhone API directly, it just happens to allow developers to use C# instead of Objective-C. No translation necessary. Even Adobe Flash apps being recompiled for the iPhone isn't a big deal. A high quality Flash game like Bejeweled, for example, is going work great on the iPhone if Adobe did their job right. That is an opportunity for you to have apps you wouldn't otherwise have and it's not wasting programmer resources rewriting it to achieve the same result for nothing. Rule 3.3.1 does not mandate high quality applications. If you want that, make Apple use their approval process for that instead of their own selfish interests. This rule does nothing to give you want you want.
- metageek 17y ago"Microsoft has had a Mac development team since the very first Macintosh. They write native software that is not a port of the Windows versions." Minor nit: these two statements are true separately, but misleading together. Many of MS's early Mac programs were written to a bytecoded abstraction layer. The results were distinctly non-Mac-like, which is why MS eventually switched to fully native apps. IIRC, this was true from the very beginning, while Jobs was still in charge the first time. Here's an anecdote from Andy Hertzfeld that mentions the abstraction layer in passing: http://www.folklore.org/StoryView.py?project=Macintosh&story=A_Rich_Neighbor_Named_Xerox.txt&topic=Microsoft&sortOrder=Sort%20by%20Date&detail=medium http://www.folklore.org/StoryView.py?project=Macintosh&s...