Not just to share code, but developers and other parts of the language ecosystem as well. From my perspective Swift is in a trailing group with Go and Rust, ch

Not just to share code, but developers and other parts of the language ecosystem as well. From my perspective Swift is in a trailing group with Go and Rust, chasing C# and Java for new server/service development. Swift is behind, IMO, in supporting server-side development, but ahead in language adoption. That's why the SSWG makes sense. (Probably C/C++ is used for a lot of new server development too, but I feel that's mostly unassailable, at least directly -- I think that's mostly on-going development in systems with heavy ties to existing C/C++ projects where they've already very seriously considered alternatives and rejected them.)