|
|
|
|
|
by mahyarm
3388 days ago
|
|
I don't use swift in a backend context, but from the iOS side: * The debugger & indexer fails often. * Build times are slow and source kit (the 'IDE features' server/library) has performance/stability problems. * Scaling your CI is pretty bad since your stuck with apple hardware & their OS. There isn't an 'AWS' for apple hardware. MacStadium is so-so. * You also don't have full control over your build chain, and decisions made by apple xcode can screw you over in when they change something in an update. * Migrating your code from one version to the next can be a multi-week event. I wouldn't use swift until it matures as a language in a few years. On backend you rarely need something that is not garbage collected. I would stick with python, golang & java. Maybe use rust or C++ if you need it. |
|
While I agree with most of your criticisms I'll say it's never taken me more than an hour to update any code base when Swift versions change, it's a mostly automatic process.
Also I'd say anyone doing iOS development in Objective C instead Swift nowadays is doing themselves a grave mis-service. It's much easier and faster to build higher quality apps in Swift.