5 Comments
- jsnover, on 10/12/2007, -0/+1> I gave up Windows PowerShell and went back to Cygwin
You don't need to choose. You can run Cygwin commands and utilites from withing PowerShell giving you the best of both worlds.
Jeffrey Snover [MSFT]
Windows PowerShell/MMC Architect
Visit the Windows PowerShell Team blog at: http://blogs.msdn.com/PowerShell
Visit the Windows PowerShell ScriptCenter at: http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx - aabs, on 10/12/2007, -0/+0Hi Shestowitz,
I am independent of Microsoft, have never worked for them, and probably never will (unless they make me an offer I can't refuse). But I do refer you to this:
http://aabs.wordpress.com/2006/12/05/dodgy-postmodernist-analysis/ - aabs, on 10/12/2007, -0/+0Jeffrey,
Sorry to have given offence. I've tried to explain why I opted out of using powershell for the time being in the post below. In the original post (above) I was trying to establish my non-corporate credentials ;-) I.e. I was hoping to give the impression that I had done my fair share of development on Vi/Make oriented development environments. I didn't mean to imply that powershell was in any way inferior to cygwin, just that cygwin was an old-skool environment that I am still fond of.
It didn't occur to me to try setting powershell up to use cygwin. In fact I'm not sure how I'd do that, but I resolve to give it a try!
http://aabs.wordpress.com/2007/02/04/powershell-not-inferior-to-cygwin/ - schestowitz, on 10/12/2007, -1/+1This whole thing is a classic piece of Microsoft FUD. Have a look at the following:
Visual Development on Linux
,----[ Covering... ]
| QT
| Gambas
| Nvu
| Eric
| Eclipse
| JDeveloper
| Planner
`----
http://openubuntu.blogspot.com/2006/11/visual-development-of-linux.html - lurpitus, on 10/12/2007, -1/+0Everyone should know by now that PowerShell is far superior to any other shell when it comes to scripting. You can do just about anything with it since it is basically same as coding with .NET language, only a bit easier. With traditional shells like bash you usually just do cat/grep/ls this and that and then pipe the output to some other command which then reads the input and generates another type of output. This means that the functionality of the script is tightly coupled with the input/output of the different commands. With PowerShell you can just take directory object and you'll have all the information right there. No need to pipe anything.
Some basic examples: http://blogs.msdn.com/powershell/archive/2006/04/25/583272.aspx


What is Digg?
The Digg Toolbar for Firefox lets you Digg, submit content, and keep track of Digg even when you're not on the Digg site. Download the official