4 ms·

This was a bit of a bust for me as well. Talking about Apple's web services being terrible and then slamming the technology that has made them oodles of money

This was a bit of a bust for me as well. Talking about Apple's web services being terrible and then slamming the technology that has made them oodles of money and rarely - if ever - has problems... It seemed a bit extreme.

Aqua_Geek 14y ago
> Talking about Apple's web services being terrible and then slamming the technology that has made them oodles of money and rarely - if ever - has problems... You can make oodles of money off of crappy infrastructure[1]. The fact of the matter is that Apple's web services really are terrible – especially from a developer's perspective. Why do I have to use Apple's tools to add a device to my iOS Developer account[2]? Why isn't there an API for retrieving reviews for my apps? (Yes, I know about the RSS feed – it's terrible and currently broken once you get past page 10.) Or app rankings? Why isn't there an API to retrieve my app sales reports? Why isn't there an API to iTunes? (Yes, I know about the Enterprise Partner Feed – that's not the same thing.) Don't even get me started about Radar, their bug reporter[3]. The list goes on and on. 1. The infrastructure isn't necessarily "crappy" for them – it apparently works well enough for them internally. The problems begin once you try to interface with them as a third party. 2. There are some web scraper tools that allow you to do this, such as @mattt's Cupertino: https://github.com/mattt/cupertino/ https://github.com/mattt/cupertino/ 3. bugreporter.apple.com
- skyebook 14y ago
  Crappy infrastructure != crappy code and web application design. - No API for app reviews? Business decision. - No API for app rankings? Business decision. - No API for... you get my point. If apple saw a reason to have these things, they'd have them. Blaming the WebObjects stack just _doesn't_ make sense. bugreporter.apple.com? I'm with you, it needs to go the way of its 10 year old capsule buttons.

Aqua_Geek 14y ago

> Talking about Apple's web services being terrible and then slamming the technology that has made them oodles of money and rarely - if ever - has problems... You can make oodles of money off of crappy infrastructure[1]. The fact of the matter is that Apple's web services really are terrible – especially from a developer's perspective. Why do I have to use Apple's tools to add a device to my iOS Developer account[2]? Why isn't there an API for retrieving reviews for my apps? (Yes, I know about the RSS feed – it's terrible and currently broken once you get past page 10.) Or app rankings? Why isn't there an API to retrieve my app sales reports? Why isn't there an API to iTunes? (Yes, I know about the Enterprise Partner Feed – that's not the same thing.) Don't even get me started about Radar, their bug reporter[3]. The list goes on and on. 1. The infrastructure isn't necessarily "crappy" for them – it apparently works well enough for them internally. The problems begin once you try to interface with them as a third party. 2. There are some web scraper tools that allow you to do this, such as @mattt's Cupertino: https://github.com/mattt/cupertino/ https://github.com/mattt/cupertino/ 3. bugreporter.apple.com

skyebook 14y ago
Crappy infrastructure != crappy code and web application design. - No API for app reviews? Business decision. - No API for app rankings? Business decision. - No API for... you get my point. If apple saw a reason to have these things, they'd have them. Blaming the WebObjects stack just _doesn't_ make sense. bugreporter.apple.com? I'm with you, it needs to go the way of its 10 year old capsule buttons.