Skip to content

Comment on Microsoft Corporation sponsors IPythonparent

Comments

If they were embracing Python, they would replace PowerShell with Python. :)

PowerShell and Python both make fairly lousy CLIs out-of-the-box, and you can already talk to .NET objects in Python through either IronPython or pywin32's COM interop, depending on what you're up to. In other words: you can already use Python in place of PowerShell. Do so in good health, and be merry. :)

Every time you have to add a new component to a system to run your tools, a system administrator gets his wings.

PS is built in, Python isn't, so Python can't be used to 'bootstrap' anything from the ground up in Windows. If you're going to have to bootstrap in PS, why not just stick with it?

Because Windows is going away. Python experience is portable. Your tools have a chance of having some use after your last Windows box is turned off.

Windows on the desktop is going away? Pretty sure it will be around for many many years to come. I say this as a primarily mac household.

That said, yes, Python is a portable skill.

But python tools are not (by default) portable when they deal specifically with OS stuff. The paradigms are too different - you have to spend considerable amounts of time doing 'if os==linux:elif os==windows' if you want portability for that kind of thing.

And to say 'windows is going away' is hilarious - maybe in the Valley, but def. not in big orgs.

Or pre-install Python on Windows like in all the other operating systems.

Yeah, it takes like 15 seconds.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.