Inside the Windows Console
I like the post, it seems like they are good guys doing a good work on an unrewarding application.<p>It is interesting the insight thet are giving with this article:
- MS is improving on Windows Console only because of WSL
- the design of the Windows Console was flawed since the beginning and remained unchanged to something like 30 years.
  Flaws includes:
  - using Console API instead of sending characters &#x2F; cannot work remotely
  - the shell and the terminal are not clearly separated: the OS will open automatically a console for some kind of executables &#x2F; cannot attach a shell to an arbitrary console<p>It seems to me that it shows a few things.<p>First, unix design was better as it was more flexible and lasted over time and computers evolution. Windows&#x27; design was sort of wrong since the beginning but they didn&#x27;t change anything and developers were left to use one of their horrible APIs. This is similar to the difference between X Window and Win32 GUI API.<p>Second, MS does not care about developers except for the user of their flagship product Visual Studio. They put 30 years of developer effort solely on Visual Studio and nothing else. Compare with Apple, they at least cared of implementing an excellent terminal and contributed greatly to the wonderful LLVM compiler infrastructure.<p>So, okay some improvements might lands on Windows 10 at some moment but I personally don&#x27;t care. At work we still use Win 7 and I think we will keep using it for a long time. The Windows Console is just horrible to use and propram for and a testament to the MS awful software and APIs that developers are forced to use because of Windows dominance.