Report from the field: porting our 30k of Swift to Swift 2 took the eminent a solid week; and we still have some bugs. Yikes. :/
Conversation
this… was not by far the worst thing I’ve had to deal with lately. So yes, I’d take this over other actual _bugs_.
1
5
I'd always favor progress despite transition cost over technical debt created by fear of making users upgrade.
2
13
take UIKit for example: I think all the work put into keeping backwards compatibility hurts complexity.
2
8
would you have preferred to rewrite for a hypothetical UIKit-replacement vs objective-c-replacement?
1
1
that is an interesting question. i don’t think the uikit-replacement could have been excellent in obj-c :/
2
2
for example async/await which attacks the heart of a lot of issues and is now neither in Swift nor ObjC
1
Replying to
Replying to
sure but if I look at ways iOSX breaks for me today, its that clearly nobody is handling async events:
1
1
That is a very good point. async/await isn’t my solution of choice, but think you’ve identified clear problem
1
Replying to
2
Replying to
at a very fundamental level basically all animation code in iOSX is incapable of handling cancellation or interruption
2