Geoff Posted January 16, 2012 Posted January 16, 2012 Well I think we've been given fair warning and we can experiment with it in advance with server core 2k8. So I don't really see why people are complaining. The benefits greatly outweigh the drawbacks when viewed objectively. I guess people don't like change.
gshaw Posted January 16, 2012 Posted January 16, 2012 CLI on the server itself would be OK if the remote management tools cover everything we need to do. Memorising huge lines of Powershell code to do mundane tasks that can be achieved with 2 mouse clicks doesn't seem to make the OS more efficient to me... giving choice is one thing but any massive shift from one extreme to the other isn't a good idea. Reference: Exchange 2007... most of the GUI ended up being put back after complaints when it was mainly Powershell
glennda Posted January 16, 2012 Posted January 16, 2012 Having worked with windows pre using linux working from the command line and text files is about 1000% easier. Whereas with windows its always trying to find that checkbox which makes everything hunky doory. If its in the text file correctly it should work. Also means resolving issues is easier - compare the windows forum on here with the unix one - the unix one you can paste your conf file somebody can check it - with windows its screenshots and what not which is just a pita!
Earthling Posted January 16, 2012 Posted January 16, 2012 I am just wondering, why will is still be called windows withough the GUI, should it not, in theory, be MS-DOS Version 8.x Server Edition at this rate. That was my first thought. My second thought was that they can do what they like, cos I'll be retired by the time it comes out.
pete Posted January 16, 2012 Posted January 16, 2012 So I don't really see why people are complaining. The benefits greatly outweigh the drawbacks when viewed objectively. I guess people don't like change. You realise that Microsoft will do their usual, right? 1) Oops, we forgot to include searchable command history that persists across different CLI sessions. 2) ....and we also forgot to include command tab-complete using your path settings. 3) ....no, we didn't include a vim/nano-a-like (or re-issue edit for the 21st century. And you'll be throwing things at them like everyone else. I don't really care about the loss of the GUI. What I do care about is losing the GUI for a poor CLI.
CyberNerd Posted January 16, 2012 Posted January 16, 2012 I don't really care about the loss of the GUI. What I do care about is losing the GUI for a poor CLI. ^ they've had the last 36years to perfect it though - they should be able to do that right as there are enough decent shells out there that they can copy.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now