[ehaughee]

As a .Net (work) and FOSS* (free time) developer, I find that the ecosystem just doesn't require the use of the CLI nearly as much. Sure, you can interact with TFS from the CLI (and maybe it's better, I don't know) but the first exposure most have to it is GUI so you learn that way. That's just one example but Visual Studio et. al. tend to take care of many things I use the CLI for on OS X/Linux systems, via a GUI. I'm certainly not saying it's better but it is better than most CLI-gone-GUI tools I've used in the FOSS world. I think this is because Windows dev tools are built for the GUI first (and often have a complete lack of, or a lacking support for, CLI UX) first as opposed to many FOSS tools that assume an understanding of the CLI and are built for that first. Personally I enjoy CLI and, while it has a steeper learning curve, I am more productive with my definition of a "proper" CLI (bash, zsh, etc.) than without. So I am attempting to learn Powershell in order to regain some of lost productivity on Windows. But, that's just me. I know many .Net devs that don't feel that productivity loss without a CLI.

* I use Ruby, Python, and Javascript/Node.JS on a Mac for side projects.