> Having to setup a whole new environment just to have their fav code tool at hand or having to boot a virtual machine each time just to use it it's much more inpractical
VMs are part of the modern developer landscape and are actually quite trivial to setup. Further, once your VM is built, it requires no further effort beyond the couple clicks it takes to boot up the VM and shell (especially because most developers avoid reboots).
> As you said the fact that you are advocating that people should not be able to use Ruby on Windows just feels a bit of a nix nerdy-bubble biased thought.*
I think it's pretty obvious that I'm not advocating programmers shouldn't be able to use Ruby on Windows, they should use whatever they want, but I think they should also temper their expectations with the reality that Ruby on Windows is a pretty small niche, especially for web development (likely the most common use-case for Ruby).
Except for educational purposes, if you're a programmer, I just don't see a reason to fight one's tools by deploying them in an environment they just aren't optimized for in practice.
Ruby presents itself as fun-to-code-in programming language.
And it is very much so. That's why a lot people like using it.
Having to setup a whole new environment just to have their fav code tool at hand or having to boot a virtual machine each time just to use it it's much more inpractical, introduces overhead (e.g. sending files on which to work on with Ruby to the VM) and basically, for reasons I am sure you know, does not feel the same than having it installed locally.
As you said the fact that you are advocating that people should not be able to use Ruby on Windows just feels a bit of a *nix nerdy-bubble biased thought.