4 ms·
Problem is legacy software tends to use XML. iOS can be considered legacy at this point. Plists are prevalent at every level of iOS.
by 0x8BADF00D 6y ago
Problem is legacy software tends to use XML. iOS can be considered legacy at this point. Plists are prevalent at every level of iOS.
- qubex 6y agoAs somebody who was already a high school student deeply ‘into’ computer technology at the time, I perfectly remember the hype and release of XML. IOS was released last week by mental accounting standards. To hear both be branded as ‘legacy’ is, frankly... well, it makes me feel ancient.
- stepanhruda 6y agoXML came out in 1998, iOS in 2007 (or a year later for the SDK). It’s closer to XML than to today.
- loeg 6y agoYou shouldn't feel too ancient, as the label is grossly misused by GP in characterizing iOS and XML :-).
- azinman2 6y agoSo much has been rewritten you can’t really call it legacy at this point.
- 0x8BADF00D 6y agoFair enough. When I worked for Apple, I would often take a gander at the iOS source code. There was a lot of legacy stuff in there, as in, "do not modify this method, we don't know what it does" in comments. There were certainly legacy components in there from many years back, and it didn't seem like tech debt was on the radar. At least when I was there.
- saagarjha 6y agoAs someone currently taking a break from reverse engineering the internals of CoreGraphicsServices on macOS, I can't resist saying that iOS can't possibly be as legacy as this.
- azinman2 6y agoCertainly there are various bits that are legacy and behave like that, but generally speaking, calling the entire thing legacy is a bit of a stretch. Also considering it started in 2007, I think the definition of legacy is quite short termed here. It also implies a negativity, that if you’re not jumping from technology to technology then you’re doing something wrong. I disagree with that viewpoint.