Yep, proper Windows support is a must for easy to use dev setup - Go is OK'ish in this sense but Crystal is currently really difficult to get running (either vm or Win10 Linux sub-system or Cygwin hack needed!)
Thanks. Still wondering what the reason is though - but based on what you said, it seems like POSIX-like APIs being needed may be the reason. Maybe for the concurrency features or other language / library features of Crystal. But then again, Go has concurrency features but works on Windows, and of course Windows has threads anyway, which are usable from C/C++ and other languages.
It's simply a lack of manpower to port to the windows APIs. There's a partial windows port, but it needs a lot of work before it's merged into master.
BTW, with a bit of fidgeting, it's possible to get Visual Studio Code for Windows to use Crystal for WSL quite nicely. On the other hand, Crystal in a VM is faster.