Re:Apple’s WWDC-Closing ‘Fuck You’ to iPhone Developers
by nuclear_eclipse on Tuesday June 16, 2009 @11:59AM
(#660387)
In this case, it's a game, and there was a feature release with some new configuration options, and then two days later, a bug-fix release for one of the options under certain user conditions. In this case, maybe the bug could have been prevented, but the fact that the developer was able to get a fix release turned out in a very reasonable timeframe is what's important.
Shit happens, and updating to fix a bug should not have a two-week latency where some reviewer could all of a sudden decide that your app is now rejected or no longer meets some amorphous criterion.
Re:Apple’s WWDC-Closing ‘Fuck You’ to iPhone Developers
by Andys on Tuesday June 16, 2009 @07:39PM
(#661110)
Are you joking? I can't tell.
This is the age of web applications and permanently net-connected smart phones. Who are you to tell me I can't fix a typo or push a bugfix more than once a week?
Re:Apple’s WWDC-Closing ‘Fuck You’ to iPhone Developers
by cstejerean on Wednesday June 17, 2009 @10:49AM
(#661898)
No, not joking. I understand that you can fix a website instantly and as often as you like, but these are not websites we're talking about, they are applications that users have to download and install. If any desktop application I ran had multiple bug fix updates per week every week I would be pretty worried about the overall quality of the application and of their development process.
Not sure if having to update the same app multiple times in one week is something I'd like to do as a consumer. I like the release early, release often strategy for development, but when the app is running on someone else's device I'd like to see people put a little more attention into the quality of the software they ship. Why exactly does someone need to update their app multiple times in one week?