21–30 of 186 posts
Can someone with Swift experience comment on the status of Swift on non-Apple platforms? Is it being used outside of the Apple ecosystem? How is the tooling, deployment, availability/support, etc.
I've never actually seen it in production though, nor have I heard of any of my friends companies either
Earlier quoted context omitted.
I want to know the opinion of managers about what they think when they have to rewrite the app everytime there is a new release. I remember all the time the iOs developer spent with every iOs release. He didn't look any happy
You don't have to "rewrite the app". You run the migrator, then fix up what it didn't migrate. Swift 3 was notorious for having migrator issues, largely due to the fact that it was a pretty radical change and a huge number of method names were changed. Personally, on our hybrid app, the migrator did about 1/3rd of the work, and I did the rest, without any other engineers' involvement. Overall it took maybe 3 days to…
Seems like things are not that bad now. But stills scares me that with every new version you lose a developer for some days (or weeks).
I wish more effort were being made to make it a first class citizen on non-Apple platforms. With the popularity it has enjoyed, it could easily challenge the likes of Go, Python or even Java for server side programming.
You should definitely try rust, it's better than its counterparts, rapidly growing, memory safe language with utmost priority on efficiency. Plus its cross-platform too :)
I wish more effort were being made to make it a first class citizen on non-Apple platforms. With the popularity it has enjoyed, it could easily challenge the likes of Go, Python or even Java for server side programming.
You should definitely try rust, it's better than its counterparts, rapidly growing, memory safe language with utmost priority on efficiency. Plus its cross-platform too :)
Can someone with Swift experience comment on the status of Swift on non-Apple platforms? Is it being used outside of the Apple ecosystem? How is the tooling, deployment, availability/support, etc.
Can someone with Swift experience comment on the status of Swift on non-Apple platforms? Is it being used outside of the Apple ecosystem? How is the tooling, deployment, availability/support, etc.
How good is the ecosystem for server side applications on other OS?
I like the syntax of Swift, it would be awesome to be able to use it for iOS apps as well as server apps.
Maybe someone will explain this to me. Does Swift use this confusing "rapid release" versioning? Does Swift 4 break backwards compatibility with Swift 3? In my company people are looking for a language to rewrite some legacy Objective-C to. Swift is often discarded as "unstable" because of these major version bumps. Compare this to Go, which, seven or so years after the initial release is still 1.x and still doesn't…
https://blog.golang.org/introducing-gofix
Swift 4 had very few changes. Most Swift 4 code “upgrades” without any changes.
I’ve got two dozens Swift examples that were easy to convert to Swift 4.
Can someone with Swift experience comment on the status of Swift on non-Apple platforms? Is it being used outside of the Apple ecosystem? How is the tooling, deployment, availability/support, etc.
Earlier quoted context omitted.
> Do people enjoy rewriting code? No, of course not. The way I see it, Swift is scared to go the "Java" route where backwards compatibility is valued above all else, leaving the language an antiquated mess.
I want to know the opinion of managers about what they think when they have to rewrite the app everytime there is a new release. I remember all the time the iOs developer spent with every iOs release. He didn't look any happy
I wish more effort were being made to make it a first class citizen on non-Apple platforms. With the popularity it has enjoyed, it could easily challenge the likes of Go, Python or even Java for server side programming.
Swift is open-source. You are welcome to contribute support for other platforms!