Outside of iOS, is there really any traction for Swift development? It certainly feels like it is settling into an also-ran position. And really, mobile apps are turning out to be a dead-end, and people don't seem to be actually investing in native clients anymore, they just slap their website in a browser control.
As an Apple fan and a programming language nerd, I have basically no interest in ever using the language. I spend a lot of time in C++, Haskell, Rust, and Kubernetes, but Swift just feels pointlessly complicated to me. (C++ I think is also pointlessly complicated, but the rest at least have a point ;-)
IBM Stops Server Side Swift Framework Development
11–20 of 99 posts
Re: IBM Stops Server Side Swift Framework Development
#12Re: IBM Stops Server Side Swift Framework Development
#13Re: IBM Stops Server Side Swift Framework Development
#14Re: IBM Stops Server Side Swift Framework Development
#15While it's sad to see IBM go, Vapor and the Swift Server working group are alive and more active than ever https://github.com/vapor/vapor/ https://swift.org/server/ Amazon has also created a Swift web framework: https://github.com/amzn/smoke-framework
Re: IBM Stops Server Side Swift Framework Development
#16Does anyone know why IBM initially decided to throw some weight behind Swift?
Re: IBM Stops Server Side Swift Framework Development
#17What are other promising future "end-to-end" (i.e. Web / Server / Mobile) development platforms are there? IMO these are the main contenders:
- JS / node.js / React Native (Android/iOS) (+ other transpile 2 JS langs, e.g. TypeScript, Clojure, Scala, OCaml, etc)
- Kotlin to JavaScript / JVM / Android / Kotlin Native (iOS)
- C# Blazor / ASP .NET Core / Xamarin (Android/iOS)
- Dart JS / Dart VM / Flutter (Android/iOS)
Rust/Go/C++ could get some mentions, but I don't think they have enough community or commercial backing to become a popular mainstream option.Re: IBM Stops Server Side Swift Framework Development
#18Apple really ought to invest more in server side Swift directly themselves. I feel like it has a lot of potential, and what the community has done with limited resources is impressive, but it's not really going to be able to gain substantial traction without a lot more weight behind it imo
Swift itself still needs time to mature, too. Things like the memory model, async/await, generics, etc. The future is bright, it will just require some patience to get there.
Re: IBM Stops Server Side Swift Framework Development
#19Curious what this means for Kitura. Last I checked, the three major serverside Swift frameworks were Kitura, Vapor, and Perfect. Perfect doesn’t look like it’s under active development, and if this means Kitura stops being maintained, it’s down to just Vapor as an active project.
I do find Golang has fill microservice space where Kitura couldn’t gain traction.
Re: IBM Stops Server Side Swift Framework Development
#20Pretty clear signal that there's low appetite for full stack development in Swift. What are other promising future "end-to-end" (i.e. Web / Server / Mobile) development platforms are there? IMO these are the main contenders: - JS / node.js / React Native (Android/iOS) (+ other transpile 2 JS langs, e.g. TypeScript, Clojure, Scala, OCaml, etc) - Kotlin to JavaScript / JVM / Android / Kotlin Native (iOS) - C# Blazor /…