I love stretching my terminal on unix. What is the history or reason behind windows lame command line?
相关问题
- Does specifying the encoding in javac yield the sa
- String Manipulation with case sensitivity
- Execute command with Excel macro and close cmd win
- Sails.js - PATH variable - sails command not recog
- ExtJS 6 - pivot without CMD
相关文章
- 在vscode如何用code runner打开独立的控制台窗口,以及设置好调试模式时窗口的编码?
- Command line escaping single quote for PowerShell
- Set variable in “if” block
- How can I get a password containing a caret (^) pa
- color single lines of ASCII characters with batch
- Convert Text to Table (Space Delimited or Fixed le
- Cmd/PowerShell/SQL server: Is there any way to see
- Batch file progress percentage
Because improving the usability and functionality of anything that Unix/GNU-like development requires will undermine Windows as a commercial platform for Microsoft's partners. Preventing this means other large companies' products for developers, such as improved terminals, and other general third party products, like word processors, video players etc. aren't competing with existing Unix/GNU software. Without this, Windows wouldn't be a profitable platform, and Microsoft would lose its desktop monopoly.
This is why the terminal sucks, there's no POSIX API, no C99 support in MSVC and the list goes on. To clarify, common Unix/GNU technologies and development are intentionally unsupported so that large commercial software houses don't have to compete with them.