There are some things in Swift that definitely are not as easy going as on Golang. Swift I think, at least offers a good starting point (the bits are there), but it is so hard to find good Swift documentation or blog posts that are not centered around the idea of making an iOS app. Even trying to find decent blog posts where someone shows off or talks about writing command line macos apps is virtually non-existent. Swift for sure, has the building blocks to do it, but you really gotta dig to find that stuff.
As an example. I have been dabbling with controlling my Roku from a watchOS app. Roku devices respond to a call on 239.255.255.250:1900 with a SSDP packet over UDP. Try finding good and recent tutorial on doing UDP programming and it is non-existent.
Re:Swift Ownership Manifesto
by doctor_eval on Wednesday June 07, 2023 @07:23AM
(#36225473)
Yeah, I guess that’s my point. Most people use Swift for building apps, but anything else like servers or CLIs and all the tutorials go nowhere, because… most people use Swift for apps.
So yeah I had a similar experience. And Go is much more aligned with my use cases so hints are everywhere.
To be clear I still want to learn Swift. But the time investment is much, much greater.
Go, by comparison, can be learned in a couple of days, and it’s trivial to build a useful CLI with it.
So from my perspective, the barriers to entry for Swift are much higher, but it’s mostly due to the domain rather than the sponsor.