4 ms·
I stopped coding seriously right around the time Swift became a thing (after a decade of Obj-C, C, Ruby, Clojure, PHP, and other nightmarish things), and always
by kenneth 8y ago
I stopped coding seriously right around the time Swift became a thing (after a decade of Obj-C, C, Ruby, Clojure, PHP, and other nightmarish things), and always thought Swift for compiled server binaries, running on linux machines would be amazing. I've followed the scene from afar, but never got the impression anything seriously caught on.
What do things look like these days that make you think server-side Swift is viable?
- briandear 8y agoVapor is the main reason. Kitura is also used, but it seems, in my opinion, that it’s not as vibrant as it was, despite IBM backing. Vapor has a pretty active community — it feels like the early days of Rails. I have started using Vapor to write microservices where I would have used Rails-api in the past and the performance is astounding but you still get the ease of use typical of Rails. The Vapor ORM works pretty great so you get ActiveRecord style sugar but with pretty great performance. Perfect is another server-side framework that is popular, but Vapor won me over because I feel like it was a more approachable community. Basically Vapor feels like circa 2006 Rails in terms of momentum. And it’s crazy fast and the toolkit seems to be evolving quickly.