3 ms·
PowerShell is very comfortable in interactive mode. For scripting, I don't get it. It's not designed to be a simple text-based glue like the bourne shell is, s
by alganet 2y ago
PowerShell is very comfortable in interactive mode.
For scripting, I don't get it. It's not designed to be a simple text-based glue like the bourne shell is, so it feels weird in many places (quoting, escaping, even more than sh is). It's very good for glueing Windows stuff though, like .NET libraries and so on.
- mike_hearn 2y agoHuh I always found that to be the opposite. PowerShell is clearly designed to be a programming language not an interactive environment. E.g. 'wget' exists but run it on its own and it doesn't save the file to disk or print it out, it prints an object as a table, which is about the most useless output possible. I know why this happens but that doesn't make it helpful. Reading about the dysfunction inside Microsoft makes it clear why it ended up this way though!
- alganet 2y agoI don't want an object oriented language to glue stuff, I want a glue language. Want the result of wget in memory instead of print or disk? Write it to memory: page_contents="$(wget -O- some_page)" It doesn't try to apply some default structure, so I don't need to rely on MS doing a fancy special wget for me that calls thousands of lines Invoke-WebRequest in the background.
- nunez 2y agoDoes the ISE still take forever to spin up?
- gavindean90 2y agoI think everyone just uses VSCode now
- briHass 2y agoThe ISE is deprecated, and MS guidance is that it should be uninstalled. Defender endpoint management flags it as a mild security risk.
- nunez 2y agoLOL what a fall from grace. The ISE was/is terrible!