Re:A former Uber engineer's disaster story
by sixstringtheory on Thursday December 10, 2020 @03:51PM
(#25378460)
One thing I was surprised not to see was a mention of their Swift 2 to 3 migration, which was terrible in my experience working on apps that were nowhere near the complexity of Uber.
Apple should have never pushed Swift as hard as it did at the time. Between the constant API changes and issues like requiring dynamic framework linkage and copying the whole runtime into every app, it was absolutely not production ready.
Re:A former Uber engineer's disaster story
by uberiosthrow on Thursday December 10, 2020 @05:08PM
(#25379441)
It was a lot of work, but we had enough staff to make it someones job for half a year or a quarter, depending on how bad the migration is. With big codebases there are other issues that pop up with every new major Xcode release that we have to migrate, mitigate or fix. For example we are still at xcode 11 because of various bugs in xcode 12. Doing the migration was annoying, but it was not much compared to all the other issues, because the fixes were tractable.
Re:A former Uber engineer's disaster story
by ehmmmmmmmm on Thursday December 10, 2020 @05:07PM
(#25379435)
That's why I call idioms idiots. If you have to learn idioms, it's an idiotic thing.
Re:A former Uber engineer's disaster story
by ineedasername on Thursday December 10, 2020 @09:58PM
(#25381758)
There is no language where full expression is possible without use of idioms that don't have direct translations in every other language.
Re:A former Uber engineer's disaster story
by microtherion on Thursday December 10, 2020 @05:37PM
(#25379745)
What do you propose as an alternative?
I love Swift. But I've been adopting it in bits and pieces over the years. It's not just that the language has changed significantly, you also have to get used to the idioms. E.g. my early Swift code often featured Pyramid of Doom patterns, and both language innovations and better familiarity with the idioms have helped a lot with this.