5 ms·
Windows 9 Core. They didn't like our GUI, so we're sure end users will love learning Powershell.
by computerJanitor 13y ago
Windows 9 Core. They didn't like our GUI, so we're sure end users will love learning Powershell.
- Pxtl 13y agoAm I the only .NET developer who doesn't get the point of powershell? "Look it's C#! But with uglier syntax. And terrible tools. But with a handful of tiny features that let it work like a command-line language!"
- mhurron 13y agoIt is a CLI. So what you're not getting is server management.
- Karunamon 13y agoHonestly i'd rather install Cygwin and manually manipulate the registry than deal with powershell.
- Pxtl 13y agoAs a CLI it's hideously baroque. It brings in all the mental overhead of OOP without the tooling needed to make OOP comfortable to work with. OOP is pleasant in .NET languages thanks to the relationship between Visual Studio and all information the .NET framework has about classes and assemblies - all the documentation around the object you're manipulating is right there. The lightweight-but-still-too-heavy Powershell ISE leaves the user completely in the dark about the .NET framework.
- tbrownaw 13y agoIt's an experiment, to see how hard it is to make "everything is an object" work as well as "everything is text" for scripting.
- deleted 13y ago[deleted]
- optimiz3 13y agoWhat you're not getting is a not-invented-here scripting language with idiosyncrasies deeply coupled to .Net. If only they had just improved the command line...rather than force every admin to learn a throwaway scripting language that adds no long term value once you use any other platform.