What is Windows?
Who uses Windows?
Why developers like Windows?
Here are some stack decisions, common use cases and reviews by companies and developers who chose Windows in their tech stack.
Tower appears to be between GitKraken and SourceTree in detail, but gave two scary error dialogs when attempting to merge resulted in a conflict. Doing the same in SourceTree just worked and showed the conflict in its handy file view that's always visible (unlike Tower's mere "Merge branch 'X' into develop" message when the commit is selected).
Both GitKraken and Tower lack the commit hash in their history overview, requiring one to select a commit to see it.
GitKraken appears to be the only Windows 10 Git GUI suitable for night shifts, but like Tower is only free for 30 days, unlike SourceTree.
I use CloudApp because it saves me so much time and energy. I use it at the very least once an hour. When Skitch was shutdown I thought my life was over! CloudApp saved the day and gave me features that Skitch didn't have.
If you write a lot of technical content (or any content for that matter) it is an invaluable tool. I'm not sure about Windows support but it integrates flawlessly with macOS. 🤘
We use Vagrant because it is the best toolchain for having a standardized development environment that is readily provisoned with just a single command on macOS, Linux, and Windows.
There's a lot of things that could be better; the thing I dislike the most is how Vagrant configuration file is a Ruby script with weird semantics around conditionals, which makes it its own special language to learn. They would have been a lot better off with the configuration approach taken by Xen (where the configuration file was a straightforward Python system).
Also, it's error messages are optimized too much for people developing Vagrant itself, and not enough for helping end users who are using Vagrant, which means one has to google often to figure out what the actual problem is.
Still, I don't think there's a better alternative for a development environment that Just Works for hundreds of developers. Docker isn't really designed for the development environment use case in my view, since it's optimized for throwing away state and getting a clean one when you make changes, and that's sometimes really not what you want. And having to SSH into a remote development environment has significant latency and editor setup costs that in my view make it a backup plan, not the main way to do things.