Swift is doing quite well, and it didn’t need Windows support to drive adoption.
That Swift isn’t as popular outside the officially supported platforms isn’t surprising and doesn’t matter. The point is precisely that it didn’t have to cater to a specific one (Windows) to achieve success.
In my mind, if I'm not developing for the iPhone, why would I use Swift?
If I need to write a CLI app, why, of all languages, would I pick Swift?
Which is a valid choice, but it doesn’t mean that it isn’t successful or that it hasn’t taken off. Swift has achieved exactly the goal it was supposed to: become the official language for Apple platforms, replacing Objective-C as the entry point.
> If I need to write a CLI app, why, of all languages, would I pick Swift?
You probably wouldn’t. Other people might, for a variety of reasons including enjoying the language itself. I write CLI apps regularly and use several languages; Swift is one of them.
Swift is practically limited on MacOs & iOS.
If we’re going to limit the discussion to languages which “can be used for writing Mac, Linux, Windows apps”, then the argument is pointless. By definition, any language which can be used to write Windows apps has Windows support. That’s circular logic.
To address the argument, it only makes sense to discuss languages which don’t have¹ first class Windows support. Everything else is irrelevant.
¹ Or didn’t but were still popular at that time.
Like provide a installer which do all the necessary setup for you, including install Visual C++ Build Tools, LLVM and other stuff.
Then the community need to update the libraries to make them run smoothly on Windows, too. But this is not that hard.
My major annoyed point for using Crystal in Windows now is the native libraries, which need extra build steps that sometime not very straight forward. But I think we can overcome it with some extra effort from the community: provide the compiled lib/dll files beforehand so other people do not have to compile the native library all over again.
This will also take time, but unlike the previous challenges, it's mostly the DX now.
many open source languages “made it” without this qualification, and I’d suggest that Microsoft has a long history of primarily supporting its ecosystem languages on its platform.
Every one of these languages' Windows support tends to lag their *nix support, and most are fairly widely deployed (my definition of "making it"). Many may support Windows now to some degree, but did not originally and not for their entire incubation period.
Early Python did not have good Windows support. Neither did PHP... which is exactly why Microsoft basically copied PHP to make ASP.
Hell, even C/C++ was basically fleshed out on Unixes long before Windows even existed.
Linux (and Unix flavors before it, as well as things like BSD) is the premiere developer OS, period. It enjoys, by far, the most languages to choose from. Windows is the developer OS only for the Windows ecosystem of technologies, which is far too limiting IMHO.
The fact that you've even asked this question makes me think you are living under a Redmond rock.
If you didn't have access to WSL, you wouldn't even be able to fully enjoy most of these languages. Which is exactly why WSL exists! No one would need it otherwise!
In fact, the only open-source language I can think of that DID premiere with first-class Windows support was Java.