4 ms·
I read "Bad user experience" but I suspect what you mean is "It not what I am used to". They (Microsoft) say that their inspiration was Korn Shell and Language
by cringepirate 6y ago
I read "Bad user experience" but I suspect what you mean is "It not what I am used to".
They (Microsoft) say that their inspiration was Korn Shell and Languages like TCL. Microsoft when they still offered Windows services for Unix, they did provide a Korn shell.
If you look at some PowerShell examples and some Korn Shell example there are quite a few similarities between the two.
So they obviously were quite aware of the options in the *nix world. I really wish people wouldn't make these sorts of claims when spending like less than a few minutes looking up the development history would dispel these ideas immediately.
Personally I really like PowerShell and I find it fun to program in whereas with bash I seem to have to always relearn it whenever I attempt to do something non-trivial. However I come from a background of programming in OOP languages like Java and C# so many it just suits my mental model better than bash.
- dllthomas 6y agoMy assessment, from a history with a lot of bash and a little, not terribly recent PowerShell, is that PowerShell wound up in a pretty common position of having a better language but a worse UX. Picking out why (wrt UI in general, not powershell in particular) is an ongoing interest...
- koffiezet 6y agoIn my (limited) powershell experience, it's a "scripting first" shell, while bash is more of a a cli-first shell. Using a powershell cli is very verbose (although pretty consistent), but using it without some sort of GUI helper if you're not familiar with it is pretty daunting.
- cringepirate 6y agoI would agree with that. I think the verbosity arguments do have some merit. I normally write scripts with the ISE or VSCode with a plugin. Also there are lots of extensions that you are kinda just supposed to know about e.g. dba-tools extensions.