Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Because backwards compatibility. I've run into stuff that doesn't working in 7.x without a rewrite.

It's just best to think about Powershell 5.1 and Powershell Core 7.x like Py2 -> Py3. Most of code works as is, some doesn't, and you should use latest when you can.

>Someone wrote some automation code that handles json payloads using powershell. When we tried to migrate to azure functions which uses 7.x by default things broke because users never cared to check sensitivity of key names.

Azure Functions are nightmare in its own. Not sure how much of that is Powershell fault vs Azure Functions.

>It’s also slow even for interpreted language standards.

Actually, it's blown Python out of the water at work. It's startup time can be painful as it's interpreting everything but once it gets going, it really moves. We use it to churn through 4GB CSV at work replacing a Python script, it's much much faster.

>I’ll seriously never use powershell for anything serious ever again even though I admit syntax and design feels kinda nice.

Your loss. Despite the few problems I run into, I really like it and wish more *nix people gave it a try. It's much better then bash nightmares I've seen.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: