News for hackers. Stuff that matters.
Re:Porting a historic Python2 module to Python3 by weberc2 on Thursday July 27, 2017 @03:39PM (#14868680)
I don't think Apple could even get away with this if Swift were more than 3 years old. I suspect the relationship between migration pain and age is exponential.
Re:Porting a historic Python2 module to Python3 by jpttsn on Thursday July 27, 2017 @05:18PM (#14869674)
In part it's age. In part, Apple get away with it because they forewarned developers. Swift explicitly intended a "move fast and break things" approach to syntax, naming etc.