Should I use Swift for my backend tech stack or should I actually learn and use Go? #Swift#Swiftlang#go#golang

as someone with a few years of professional experience in both: Go is un-ergonomic, unpleasant to use, and prone to stupid C-ish gotchas. its only advantage is ecosystem maturity. honestly Vapor for Swift is looking pretty good these days. i'd start there.

Go, or like @mackuba.eu said give hummingbird a try. but yeah I wouldn't use Swift.

I'm definitely the best person to give advice on this, having used neither server-side Swift nor Go, but the general feeling I get from what people say about server Swift is… that it's still not all the way there yet (Linux support not being as good as on Mac etc.)

Swift looks promising and may have a bright future but Go is just so good for building backends. I would say it's the ecosystem but honestly the standard library has most of what you need.