15 ms·
Not the same user, but I once tried to get PowerShell to do an ls over FTP for me, and even with copying some sample code it was horribly painful. I can't spea
by Elrac 12y ago
Not the same user, but I once tried to get PowerShell to do an ls over FTP for me, and even with copying some sample code it was horribly painful.
I can't speak from broad experience but my impression was that PowerShell does a bunch of common cases fairly well but if you want something a bit different you're bashing your head on your desk.
- oblio 12y ago> you're bashing your head on your desk Repeatedly. Powershell is a wonderful concept but the ecosystem around it, except for Microsoft's own extensions, hasn't really hit puberty. Also try writing scripts which involve native Windows commands (such as robocopy & company). Things are definitely not intuitive and the error handling is crappy. You either stay within Powershell bounds and everything is wonderful, or you step out and are in a world of pain.
- mreiland 12y agoyears ago I posted much the same sentiment on stack overflow when I was attempting to use Powershell 1 to build and deploy software that used SVN for it's SCM. It was a pain in the neck and I felt like the PS integration was awesome as long as you stayed in that ecosystem, but the second you strayed... pain. I got bashed fairly hard with the question I asked surrounding it closed as unconstructive (it was an honest question about exactly what PS was targetted towards).