5 ms·
I'm going to address each bullet: - Set-ExecutionPolicy can be set with a single click from the "For Developer Settings." Just scroll down and hit Apply three
by UnoriginalGuy 10y ago
I'm going to address each bullet:
- Set-ExecutionPolicy can be set with a single click from the "For Developer Settings." Just scroll down and hit Apply three times and your machine has sane developer defaults (inc. ExecutionPolicy).
- The verbosity means that you can "guess" PS commands. Each PS command is a set layout with an action word (e.g. Add, Clear, Get, Write, etc) and then target (e.g. Set-Alias, Set-Date, Set-Service, etc).
- A ton of people use PS. In particular SysAdmins are moving from VBS/Bat to PS in droves. No clue what communities you hang out with where nobody uses it?
- It is definitely still a work in progress. But most of the core parts of the language hasn't changed much, if you wrote a PS file three years ago it likely still works today. All they've done is add new cmdlets, new libraries, and new functionality which doesn't hurt backwards compatibility.
- rspeer 10y ago> If you wrote a PS file three years ago it likely still works today. That's a really low bar. Isn't Windows supposed to have a legendary commitment to backwards compatibility? 3 years of backwards compatibility would be nice for a bleeding-edge development environment like node.js that you can tear down and replace whenever you want, but not for your operating system shell.
- mattmanser 10y agoGuess? With naming conventions like "Get-ChildItem"? Major functionality, probably the worst name you could come up with.
- UnoriginalGuy 10y agoA single anecdote doesn't discount a trend. Being able to predict a PS cmdlet based on patterns works. I know, because I use it daily.