Great question. I'm curious about what others do as well. By day I am a .NET developer who typically uses Visual Studio. I do all of my development on an Azur

Great question. I'm curious about what others do as well. By day I am a .NET developer who typically uses Visual Studio. I do all of my development on an Azure VM with all of my dev tools on it. This is very useful because I can access it from anywhere and don't muck up a physical machine doing it. I use a standard F4 instance and stay under my free MSDN credits most months as long as I remember to turn it off (automation has fixed this recently ;). Not exactly what you mean, but lots of the same benefits. But, I do like to tinker and see what all the cool kids are using, so have tried most of the ones you mention as well. I do think this model will become way more common, but none have stuck so far for me. Most of that is that I have customers that use VS and have a hard time imagining them using anything else. But I also felt the "free SKU" on some of these to be a little limiting. One or two projects or public-only projects means I have to commit to use in my day job. I don't fault them for making money, but there is a barrier there that limits me from using or recommending it. Also, if I'm learning something new - especially tooling like webpack/grunt/gulp/yo/etc.- it can be difficult to translate "getting started" style documentation to the specific environment. If something goes wrong, I'm unsure if it's the environment or me (though I assume the later ;) As many have suggested, gomix is changing this some for me. I've used it to learn node a bit more, and as a place for one-off tests of JS/HTML/CSS issues. As with the others, I feel like I'd have a hard time recommending it for production use at the moment, but really like it for things I don't necessarily want in my or my customers' source control. It's zero-friction and "just works" for a certain class of problem. My _hope_ is that these mature so that 1) there is less vendor lock-in and barrier-to-entry and 2) get more popular so that certain types of applications don't need a full on dev environment to code for.