Linked by David Adams on Fri 5th Aug 2011 16:08 UTC
Graphics, User Interfaces A couple of days ago I read a blog post by Stephen Ramsay, a professor at the University of Nebraska-Lincoln and a Fellow at the Center for Digital Research in the Humanities. In it, he mentions that he has all but abandoned the GUI and finds the command line to be "faster, easier to understand, easier to integrate, more scalable, more portable, more sustainable, more consistent, and many, many times more flexible than even the most well-thought-out graphical apps." I found this very thought-provoking, because, like Ramsay, I spend a lot of time thinking about "The Future of Computing," and I think that the CLI, an interface from the past, might have a place in the interface of the future.
Thread beginning with comment 483946
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: Powershell vs Bash
by benjymouse on Sat 6th Aug 2011 18:18 UTC in reply to "RE[4]: Powershell vs Bash"
benjymouse
Member since:
2011-08-06

If you spend a lot of time on Windows.


Sort of agree there. PowerShell is a much better fit for Windows than other OSes, since Windows API is already almost exclusively object-oriented (handles, WMI, COM, .NET).

... that didn't exist on anyone's computers. Has that changed? Does windows 7 come with any version of the dot net framework and/or Silverlight?


With Windows 7 PowerShell is an operating system component since several tools which come with the OS are based on it (e.g. troubleshooting scripts like the one that runs when you click "troubleshoot problems" on a faulty network connection). Several new server products from MS have advanced functionality which can only be reached through PowerShell.

PowerShell is a system component since Vista SP1 - although it had to be "turned on". Since Windows 7 / Server 2008 it is a mandatory component.

Edited 2011-08-06 18:26 UTC

Reply Parent Score: 1