|
|
|
|
|
by Grustaf
856 days ago
|
|
I started using Swift right away in 2014 and worked on several large projects written in Swift 2, 3, 4. Of the three or four large migrations I had to perform, the worst one still took less than a day - unless your Swift 4 project is enormous, you should be able to migrate it to Swift 5 before lunch time, the differences are really minimal. Surely it's a good thing that a young language evolves, you can't improve without changing. And Apple were very clear about the fact that there would be breaking changes. You can of course insist on using Objective C if you prefer it, but that closes the door to most of the new APIs that are being added by Apple, which seems like a very steep price to pay for the privilege of using a legacy language. |
|
You, knowing absolutely nothing about my code: "you should be able to migrate it to Swift 5 before lunch time"
(In this respect, yours is such a sterotypical HN comment. "I could build [whatever] over a weekend.")
Moreover, even if your baseless, overconfident assertion were true, it's now about 6 hours until lunch time, and I'd rather not waste that time on a free hobby project just to make the damn Swift compiler happy.
> that closes the door to most of the new APIs that are being added by Apple, which seems like a very steep price to pay
I haven't needed anything that requires Swift, so there's been no price paid. I'm doing great. No problems! Swift proponents seem to have to tell themselves that I'm suffering in some way by continuing to use Objective-C, but I'm not suffering at all.
Regardless of language, I usually avoid new Apple API, because it tends to be half-baked and buggy.