Wondering if #SwiftLang 3 migration was really handled the right way. I get there are advantages to "ripping off band-aid" in one go, but…
I suspect combining certain changes increases migration difficulty exponentially, not linearly. Multi small migrations might've been better?
feel that reliably machine-migratable 1:1 changes like renaming should be separate from complex semantic shifts like Seq. index refactoring
Problems with the latter seem to throw off automation of the former, leading to lots of (theoretically unnecessary) manual migration :(
Especially combined with bugs in the migrator (yes, I've filed them. At least, the ones I could isolate) eg migrator just gave up midproject
Previous migrations have been hours per app, 2.2 → 3.0 was a week for the first app. Need to take a break before attempting next!
Share this Scrolly Tale with your friends.
A Scrolly Tale is a new way to read Twitter threads with a more visually immersive experience.
Discover more beautiful Scrolly Tales like this.