3 ms·
It's not rare at all. In every corporate environment I've worked in, my choices were PowerShell or 3 months of red tape, meetings, and security audits. I get t
by bongodongobob 3y ago
It's not rare at all. In every corporate environment I've worked in, my choices were PowerShell or 3 months of red tape, meetings, and security audits.
I get that in a dev shop that's not the case, but most businesses employ 0 devs. So people end up being forced into shell scripting because it's the only approved option.
- int_19h 3y agoAt least PowerShell gives you access to the entirety of .NET, even if syntax is not ideal for non-interactive use in many cases.
- bongodongobob 3y agoYup. My "scripts" end up with a lot of .NET stuff in there. I'd rather use Python, but being forced to use PS for years, I've come to like it.
- int_19h 3y agoDepending on what you're doing, C# might also be an option - since the compiler is a part of the .NET Runtime (not just SDK), it's available on any Windows install with PowerShell these days. It's too bad that the system one is always an old version that doesn't do .csx, but still.
- fargle 3y agoit's not rare, it's rare that it's the best engineering choice. if your management can't allow even a python script, but it can allow bash? then it's not an engineering problem. as you even allude - your business does not have a software engineering culture. a good engineering culture does not depend on job titles or budget or degree either. but it can't exist without healthy management.
- bongodongobob 3y agoIt's much easier to control allowed functionality in PowerShell via security policies. Python is comparatively a free for all. It makes sense in a non-dev environment.