How bad is the Windows command line really?
It&#x27;s really, really, <i>really, really</i> really bad.<p>It doesn&#x27;t even have a logical history. Despite having used it for many years, I still don&#x27;t understand why when I type one command (eg make), and then another (eg out.exe), I have to toggle between pressing up or pressing <i>down</i> from the new command-prompt to access the previous commands.<p>I can&#x27;t make the window more than 80-characters wide dynamically. (I don&#x27;t want to change settings and restart the program to get the width to change.) So any time I want to copy and paste one of the infamous wall-of-text C++ template errors, I have to waste a lot of time reformatting the text.<p>Copy-and-paste as well is just complete garbage that takes forever.<p>I have to dump batch files into a folder in PATH because there&#x27;s no alias support nor .profile startup script.<p>I can&#x27;t color-code the prompt separately for visibility. There&#x27;s no tab-completion. There&#x27;s no shell escaping backticks. On and on.<p>Batch scripts are just hopelessly broken. It really feels like we&#x27;re abusing the hell out of them to do things they were never intended to do. The language is closer to Malbolge than C.<p>PowerShell is a whole other can of worms. I don&#x27;t care for it either, but that&#x27;d be a separate discussion.<p>Bash on Windows sounded promising, up until &quot;Windows 10 only&quot; and &quot;doesn&#x27;t play nice with the regular Windows environment.&quot;