Timeline for answer to Is PowerShell ready to replace my Cygwin shell on Windows? by Mystere Man
Current License: CC BY-SA 4.0
Post Revisions
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 3, 2019 at 10:46 | history | edited | Peter Mortensen | CC BY-SA 4.0 |
Active reading [<http://en.wikipedia.org/wiki/Cygwin> <http://en.wikipedia.org/wiki/Bash_%28Unix_shell%29> <https://en.wikipedia.org/wiki/KornShell>]. Added some context.
|
| Jan 7, 2011 at 18:08 | comment | added | Erik Funkenbusch | @Xepoch - The point is, you can choose which way you want to do it. You can use all the goodness of the built-in shell, or you can ignore and do it the way Unix does it. It's your choice. And choice is good, right? | |
| Jan 7, 2011 at 18:07 | comment | added | Jé Queue | I simply don't know PowerShell enough to give you a critique thereon, but as you clearly know the goals of the Unix shells are not necessarily a fully comprehensive replacement of external tooling, rather the control structures around it. Again I cannot at this time compare nor contrast but elevating PowerShell because it has more built-ins is not necessarily the boon of the Unix shells. | |
| Jan 7, 2011 at 17:31 | comment | added | Erik Funkenbusch | @Xepoch - No, I think you're missing the design goals of PowerShell. PowerShell can do everything the Unix shells can do in the same way that they do it. However, the real power comes when you utilize PS's object piping system rather than just parsing text output. So, PowerShell can do exactly what bash or korn can do, but they can't do what PowerShell can do. | |
| Jan 7, 2011 at 17:24 | comment | added | Jé Queue | I think you may be missing the design goals of Unix shells. Not knocking PowerShell (would like to learn more myself) but you need to understand Unix tooling to make a statement like that. | |
| Feb 22, 2009 at 3:22 | history | answered | Erik Funkenbusch | CC BY-SA 2.5 |