While powershell is a valuable and interesting option, the problem with it is that it changes the basic metaphor.
For 40 years unix shells and their descendants and derivatives including cmd.exe have used files and text streams as the metaphor for interconnecting processes. Powershell changes that, and it means the output of one command goes to the input of another command as "objects".
This can be powerful, but it is also very disorienting. Which means it can be hard to learn to do even basic things in powershell, things that would take only a pipe or two and a couple unxutls programs in cmd.exe.
In cmd.exe, easy things are easy and hard things can be really hard. In powershell, hard things are hard (as opposed to "really hard") and easy things are hard.
Is this different from Unix Utils? Every gig I've ever been on where I'm forced to use a Windows box, first thing I do is load the Unix Util exes into some directory and add it to the path. http://unxutils.sourceforge.net/
I currently have to use Windows at the customer I'm working for. I've installed Console which gives tabs and better copy-n-paste on Windows. See http://sourceforge.net/projects/console/
I'm not sure if clink and Console will work together, but I'll have to try it.
I have tested and clink works with Console. Actually I don't see reason why it shouldn't work with Console. Maybe there might be shortcuts collisions but I have not met yet any.
Is it worth installing .NET 3.5 to run the ISE? I use Powershell but only have .NET 4 which runs it just fine. I'm a little surprised that ISE requires 3.5.
I love PowerShell dearly, and I miss it on Unix systems, but what this is trying to fix, and what still stinks at the moment, is the command-line editing situation in Console, which has nothing to do with PowerShell v. Bash v. cmd.exe.
as a .NET developer who sits in both Linux and Microsoft worlds, but primarily in Microsoft technologies, I must say that PowerShell is a very useful and amazing addition to Windows. I did have to learn it, but once I did, I love it.
I feel like cygwin manages to combine the worst of UNIX and the worst of Windows. And the commands that use the cygwin runtime are noticeably slower than the native counterparts.
Also, AFAIK there is no 64bit version yet, which for me is a dealbreaker (I often work with files larger than 2GB).
I've watched numerous Russian colleagues use it and it does not look appealing. These same colleagues do not seem to understand the power of a real *nix shell. You end up doing less typing if you really know your shell and how to pipe etc.
[+] [-] ehosca|13 years ago|reply
[+] [-] Graphon|13 years ago|reply
For 40 years unix shells and their descendants and derivatives including cmd.exe have used files and text streams as the metaphor for interconnecting processes. Powershell changes that, and it means the output of one command goes to the input of another command as "objects".
This can be powerful, but it is also very disorienting. Which means it can be hard to learn to do even basic things in powershell, things that would take only a pipe or two and a couple unxutls programs in cmd.exe.
In cmd.exe, easy things are easy and hard things can be really hard. In powershell, hard things are hard (as opposed to "really hard") and easy things are hard.
[+] [-] slowpoke|13 years ago|reply
[+] [-] soldermont001|13 years ago|reply
[+] [-] alttab|13 years ago|reply
[+] [-] projectileboy|13 years ago|reply
[+] [-] pudquick|13 years ago|reply
https://github.com/bmatzelle/gow/wiki/executables_list
https://github.com/bmatzelle/gow/wiki
Kept up to date, every .exe (once installed) is self-contained (no external .DLLs) and portable to just about any Windows box I've run into.
No Cygwin or MinGW installation required.
Bash is actually available in the list (albeit an older version) if you really wanted "bash on Windows"
[+] [-] Graphon|13 years ago|reply
They are complementary.
[+] [-] malkia|13 years ago|reply
[+] [-] slu|13 years ago|reply
I currently have to use Windows at the customer I'm working for. I've installed Console which gives tabs and better copy-n-paste on Windows. See http://sourceforge.net/projects/console/
I'm not sure if clink and Console will work together, but I'll have to try it.
[+] [-] ot|13 years ago|reply
I'm giving ConEmu a try and it looks awesome!
http://code.google.com/p/conemu-maximus5/
Scott Hanselman wrote a blog post about it:
http://www.hanselman.com/blog/ConEmuTheWindowsTerminalConsol...
[+] [-] daliusd|13 years ago|reply
[+] [-] rbn|13 years ago|reply
[+] [-] gouranga|13 years ago|reply
[+] [-] omaranto|13 years ago|reply
[+] [-] noveltyaccount|13 years ago|reply
[+] [-] alanbyrne|13 years ago|reply
[+] [-] gecko|13 years ago|reply
[+] [-] 7D8|13 years ago|reply
[+] [-] pygy_|13 years ago|reply
It is definitely worth it for some people, but time is a limited resource, and others will benefit from this kind of project.
[+] [-] est|13 years ago|reply
[+] [-] 38leinad|13 years ago|reply
[+] [-] ot|13 years ago|reply
Also, AFAIK there is no 64bit version yet, which for me is a dealbreaker (I often work with files larger than 2GB).
[+] [-] malkia|13 years ago|reply
[+] [-] shortlived|13 years ago|reply
[+] [-] Bjartr|13 years ago|reply
[+] [-] unknown|13 years ago|reply
[deleted]