So great, they re-introduced the features they took out 20 years ago. Wake me up when they properly support UTF-8.
Too little, too late.
Too little, too late.
The stagnation in cmd.exe (and even PowerShell) appears to be a casualty of Microsoft assuming that point-and-click would take over the world completely, which clearly hasn't happened in development. I still shake my head at the ops nightmare that is RDPing into hosted Windows Servers.
As one of the sibling posts here notes, there's really no reason to use Windows Server for anything, unless you have legacy applications to support. They're going to have to do a lot, lot more to make this a competitor.
Can you elaborate? I have all of my boxes saved in the MSFT RDP manager doodad (before which I used RoyalTS or seomthing). When I want to get on it I double click and it logs me in and there it is - a fully featured interface from which I can do whatever admin I need opening up the relevant tools etc using the point and click you dislike so much.
[0] https://www.ibm.com/developerworks/community/blogs/devops/en...
[1] https://www.thoughtworks.com/insights/blog/moving-to-phoenix...
http://forums.somethingawful.com/showthread.php?threadid=367...
That's from a ReactOS developer.
(To make line-based copying and pasting work I would imagine they had to do some quite invasive surgery at some point... the idea that the window is backed by a screen buffer that's a fixed-size grid of (attribute,character) pairs is exposed quite openly in the API.)
[1] http://stackoverflow.com/questions/388490/unicode-characters...