This is just a (mostly) positive remark ("my two cents") mainly targeting those who once tried to use Swift on Linux or Windows or were missing an IDE on those platforms. Maybe they would like to try again...
I have the impression that the cross platform experience for Swift has become quite good overall. I am successfully compiling Swift and deploying Swift code on Linux and Windows. The Swift Package Manager in particular has been working really well on Windows for some time now. For writing code on Linux or Windows, we have the following possibilities (sorry if I missed another solution):
(The first solution is free, the other is not free.)
And yes, not everything is perfect. Apple being the "Benevolent Dictator" of Swift (borrowing a term from Python) is two sides of the same coin:
On the one hand, Apple ensures that tremendous work is being done on Swift, as Swift is so important for Apple's systems.
On the other hand, and despite Swift being open sourced, Apple makes the final decision in many cases or is developing some new stuff in private first (I hope I am not too crude with this observation). And other platforms than Apple's might not have the same importance for Apple (and I know, there is a lot of work to be done).
So there might still be some issues when using Swift on non-Apple platforms (e.g. not all of Foundation is supported outside of Apple's platforms), but I have the impression that the Apple forks are taking the cross-platform task seriously (take e.g. this post by Ted Kremenek). It should also help that Apple is using Swift in many places now (including servers, I would guess that those are still mainly Linux servers), and many frameworks are not wrappers around Objective-C frameworks any more, including Foundation if I understand it correctly (see this excellent interview with Ben Cohen, especially at the end).
...And yes, maybe the cross-platform idea should be taken even more seriously (???), e.g. the Windows port is still "attributed" to @compnerd – kudos to @compnerd for the good work he is (and hopefully will be) doing, but maybe it is time for the Swift project to be committed to the Windows port "no ifs and buts"? ... As I said, only my two cents.