I think the "original" reason was probably just that the Windows command line is a tragedy, while Bash is wonderful. Nowadays, Windows itself is a tragedy.
That said, I actually use Windows because I need to scan things. This is itself a blast from the past, since the reason to use Windows back in the 90s was that there were a lot of problems with PCI 56k modems on Linux.
Graduated in Digital Media M.Sc. now developing the next generation of educational software. Since a while I develop full stack in Javascript using Meteor. Love fitness and Muay Thai after work.
It wasn't just the command line. There were problems with Windows that made some things nigh on impossible; especially in relation to node: IIRC there were limitations to path lengths and deeply nested dependency trees that broke things badly. There was also the infamous node-gyp problem: github.com/nodejs/node-gyp/issues/629
I moved to Linux exactly because of these issues...
A sane command line is now the least of Windows' issues. After all, we now have a Windows that forces you to update, forces you to associate it with a Microsoft account, and actively surveils you. On top of having an increasingly absurd configuration system.
I know there are workarounds for these things, with varying effectiveness, but you shouldn't have to work around an operating system so heavily.
I think the "original" reason was probably just that the Windows command line is a tragedy, while Bash is wonderful. Nowadays, Windows itself is a tragedy.
That said, I actually use Windows because I need to scan things. This is itself a blast from the past, since the reason to use Windows back in the 90s was that there were a lot of problems with PCI 56k modems on Linux.
Huh? Scanners work just fine with Linux. I use mine all the time. I just plugged it in - worked immediately
HP has very good Linux support with it's HPLIP driver suite. Never ran into issues.
I also use HP both pc and laptop, with Parrot OS
I would like to know the scanners name
Canon PIXMA MP240 - combined printer/scanner
I use an Epson printer/scanner, network connected, and it works just fine.
Also Epson ships Linux drivers.
It wasn't just the command line. There were problems with Windows that made some things nigh on impossible; especially in relation to node: IIRC there were limitations to path lengths and deeply nested dependency trees that broke things badly. There was also the infamous node-gyp problem: github.com/nodejs/node-gyp/issues/629
I moved to Linux exactly because of these issues...
you have have a linux subsystem on Windows, and it runs anything you want, so a POSIC terminal is no longer a problem on Windows.
A sane command line is now the least of Windows' issues. After all, we now have a Windows that forces you to update, forces you to associate it with a Microsoft account, and actively surveils you. On top of having an increasingly absurd configuration system.
I know there are workarounds for these things, with varying effectiveness, but you shouldn't have to work around an operating system so heavily.
Absolutely agree with you.
While windows is usable, it still tells you actually you don't own your system, on every opportunity they have.