I've brought this up before, but it's a mix of everything, and all pretty bad. > If you've ever poked around with the way that Apple's website works, you can s

I've brought this up before, but it's a mix of everything, and all pretty bad. > If you've ever poked around with the way that Apple's website works, you can see that the entire place is a huge mess. There's old servers running ancient (pre-2004) perl scripts alongside the brand new iCloud gear. I can't imagine how the authentication for AppleID is working as login details still work on the ancient pages (think pinstripes and glassy buttons). Depending what URL you hit, the webserver is using php3, php4, perl, python or maybe WebObjects (java). > At one point I wrote a scraper that was targeting one of their product pages, and kept getting random, unexplainable results. It turned out that one of their product areas was behind a round-robin load balancer, with three completely different apache versions on each server. The page was dying on one but not the other two. In the end I just had to repetitively scrape until I hit a good response. https://news.ycombinator.com/item?id=6078854 https://news.ycombinator.com/item?id=6078854