4 ms·
There was some discussion in previous threads about how their systems seem (like many others, to be fair) to be a taped-together mess of old perl scripts and se
by _delirium 13y ago
There was some discussion in previous threads about how their systems seem (like many others, to be fair) to be a taped-together mess of old perl scripts and server-side includes and CMSs and who knows what else. So they're probably trying to come back online with a cut-down version that presents a smaller attack surface and contains only components that have been vetted in the last 10 years, which is overall not a bad idea.
- toyg 13y ago>a cut-down version that presents a smaller attack surface ... or simply a cut-down version they know how to run. "Mhh, what did that old cron job do, again?" "I don't know; it was written by Mike, he left 3 years ago." "oh ok, so not important then." <12 hours later> "OMG OUR DB EXPLODED AGAIN! That script was clearly essential! Can you rewrite it??" "Er, I've looked at it: 2000 LOC of obscure Perl. Gonna take a while..."
- threeseed 13y agoI've worked on some of those systems. This isn't true. Most of their web apps are WebObjects/Java apps. Sure some of them would be classed as legacy but it is hardly different from most other enterprise companies. And their systems are completely separate from each other e.g. iTunes, Apple Online Store, ID auth, Developer Portal.