Well, I can only reflect as someone who recently (in 2021) started evaluating Swift on the server - definitely agree that there are friction in getting a toolchain and up and running properly (although looking forward to try a clean 5.4 soon).
I strongly believe perception is guided by visibility - just take the linked forum discussion above - VS Code should be a clear option, but how do someone who wants to do server development find that information in the first place if they don't even know there are options? Would be nice to give people a starting point.
I can only say that from my experience there was a significant visibility issue where a lot of useful information needs a fair amount of digging and perseverance.
I found tools like
heaptrack, the ability to use
TSAN, found a bunch of frameworks, had to build a custom toolchain for
LLDB to not trigger asserts (thanks @johannesweiss for assistance), just to mention a few things... I would have loved to have that in one place and would be happy to share such hints (like used custom memory allocators interposed and seen that it gives a nice performance boost for many use cases?)
How many people know that there is a Slack that can be joined?
Personally, I totally don't care about web related development, so references to various web frameworks which are plentiful is not very useful, but information about working server-side tools is useful!
(Server development !=
And to reference the talking points at the top:
- if we advertise a central Slack, we should take action items to make guides from recurring questions
Those guides could be hosted in this same repo for sure.
So I would propose something like the
Swift Server Development Guide repo ;-)