|
|
|
|
|
by sinatra
3611 days ago
|
|
Thanks for your feedback. Let me ask you a few more questions about your experience. The _nix commands/tools you're used to don't just start and end with Bash, right? What about the other commands/tools you used that still aren't in Windows? Do you spend a majority of your time in the command line in Win10 and you still don't feel limited by it? What about the horrible registry hell? Don't you sometimes need to go into the magical world of #RANDOMWORD1>#RANDOMWORD2>#RANDOMWORD3>... in the registry editor to make Windows behave the way you want to? Does Windows still automatically reboot for security updates, ignoring whatever else you might have running on the machine? |
|
Between Bash, Powershell (which is awesome), and Cygwin/MinGW, you can get access to most of the Unix commands and tools you are used to.
I highly recommend learning Powershell, which is really nice. Instead of forcing Windows to be like Unix, it's better to learn to live with Powershell for a while, and then bring in the Unix utilities if you really need them. If you give Powershell a chance, you may find that you don't want to use Bash anymore.
The main hurdle to development on Windows is application support, not command line tools. For example, there is no official Redis build for Windows. Installing Python and Ruby can be a little bit difficult on Windows compared to other platforms. But lots of other languages, including Java, are perfectly functional.