3 ms·

Powershell is a great language. I would love to see unix shells inspired by it. The associated toolset, on the other hand, is clearly not there yet. As soon as

Powershell is a great language. I would love to see unix shells inspired by it. The associated toolset, on the other hand, is clearly not there yet. As soon as you start doing real things with PowerShell, you will hit all sorts of bugs and limitations. Your mileage may vary, of course.

Already__Taken 12y ago
Remoting and signing has been a nightmare to set up on my domain but otherwise so far I'm still having a pleasant experience. Obviously the console itself is the same as cmd's which is terrible. I just work a lot with the ISE open but still looking for a slicker terminal. I've been able to just deploy PS v4.0 across all of my computers I think a lot of the headache comes from trying to use new stuff and seeing windows 7 ship with v2.0 I'm curious what kind of things you're running into, I'm getting quite immersed in using PS all over.
- joelthelion 12y ago
  Well, what you said, crappy console, no ssh (the powershell equivalent is just not very good), but also, no grep (findstr is not a good substitute), no rsync, etc. Whatever I've attempted I've always hit unexpected walls due to the unavailability of tools we take for granted with linux.
  - Already__Taken 12y ago
    I'll parrot one of the PS developers; "grep, sed and awk etc are really great on nix because they're great with text, they're text based operating systems and you can do anything with them. Windows is an API based system so just moving text around doesn't get you very far." There's a mountain of filters available in the cmdlets parameters but specifically since you mentioned grep. findstr is not powershell it's in the old cmd family of programs still in your PATH. You want to look at select-string http://technet.microsoft.com/en-us/library/hh849903.aspx http://technet.microsoft.com/en-us/library/hh849903.aspx I wish MS would include SSH but the party line is they've no idea who really wrote the code and they won't include it in windows in case they get sued over it.

Already__Taken 12y ago

Remoting and signing has been a nightmare to set up on my domain but otherwise so far I'm still having a pleasant experience. Obviously the console itself is the same as cmd's which is terrible. I just work a lot with the ISE open but still looking for a slicker terminal. I've been able to just deploy PS v4.0 across all of my computers I think a lot of the headache comes from trying to use new stuff and seeing windows 7 ship with v2.0 I'm curious what kind of things you're running into, I'm getting quite immersed in using PS all over.

joelthelion 12y ago
Well, what you said, crappy console, no ssh (the powershell equivalent is just not very good), but also, no grep (findstr is not a good substitute), no rsync, etc. Whatever I've attempted I've always hit unexpected walls due to the unavailability of tools we take for granted with linux.
- Already__Taken 12y ago
  I'll parrot one of the PS developers; "grep, sed and awk etc are really great on nix because they're great with text, they're text based operating systems and you can do anything with them. Windows is an API based system so just moving text around doesn't get you very far." There's a mountain of filters available in the cmdlets parameters but specifically since you mentioned grep. findstr is not powershell it's in the old cmd family of programs still in your PATH. You want to look at select-string http://technet.microsoft.com/en-us/library/hh849903.aspx http://technet.microsoft.com/en-us/library/hh849903.aspx I wish MS would include SSH but the party line is they've no idea who really wrote the code and they won't include it in windows in case they get sued over it.