Hacker News Reader

Comment by yardie | Hacker News Reader

> The Hyper-V PowerShell cmdlets that wrap the underlying Hyper-V WMI provider are well maintained and provide complete access to many settings not properly exposed in Hyper-V Manager.

I'm very familiar with Hyper-V, HVManager, and SCVMM. If you want to do anything more than a light touch deployment of a VM you're going to use Powershell. Microsoft has made that abundantly clear and even their training courses have you deploy through PS. SCVMM adds a nice wrapper with some additional orchestration. And it also adds a whole other library of PS that are also not exposed in their very advanced Windows SCVMM GUI.

This is a cool experiment but completely unnecessary. You can write a Powershell GUI with the settings and options that you prefer. It's what I've done when I wanted to see nice tabular view of VM resources that the existing GUIs could not give me. Give in to Powershell!

View on HN

Powershell is pretty awesome in Windows but it melts a lot of traditional Unix hacker brains from my experience.

You really have to buy into it and that's a hard sell for those who aren't Windows power users.

If you're doing Windows administration, PowerShell is a must; the Windows GUI is too limiting.

It is easier to approach it, if instead of trying to see UNIX everywhere, one thinks of the REPL environments from Xerox PARC/ETHZ, or even AmigaDOS with REXX.

Former Windows Admin who still uses Powershell on *nix. Once you get over the hump, you will find it's pretty darn good scripting language. Personally, I find it much more maintainable since verb-noun is clunky while writing but much easier to read.

For me my brain can NOT stop trying to use it as a CMD replacement. The CMD commands just do not work (duh its not CMD!). I then have to have that 'kerthunk' spot where I try to use the newer commands. Nothing wrong with powershell. It is just my brain for some reason can not let go of CMD in this context. Jump to bash no sweat. But for some reason my brain just will not use powershell correctly and I have no idea why. Great scripting lang and way better than bash or CMD script.

I actually love PowerShell and use it extensively to automate Hyper-V labs, but there's a big difference between automation and one-off things like a checkbox to enable nested virtualization. There's also a large portion of users looking for something just good enough as a desktop GUI to manage just a few VMs with no automation, and Hyper-V Manager is definitely behind when compared to VirtualBox or VMware Workstation in that regard.

Fair point, but these people probably also don’t administer Hyper-V environments.

As far as I'm convinced, PowerShell isn't a replacement for an interactive shell, it's a Windows-native replacement for Python.

Reply on news.ycombinator.com