4 ms·
And in what is starting to seem like a pattern, Microsoft makes a public move to do the Right Thing. >jpsnover commented ... @bagder You bring up a great point
by wyldfire 10y ago
And in what is starting to seem like a pattern, Microsoft makes a public move to do the Right Thing.
>jpsnover commented ... @bagder You bring up a great point. We added a number of aliases for Unix commands but if someone has installed those commands on WIndows, those aliases screw them up. ... We need to fix this.
> Snover is a Technical Fellow at Microsoft & the inventor of Windows PowerShell ...
The thread goes on at length about bureaucratic requirements for the change. I guess this is what happens when you hold a bazaar inside the cathedral.
- patrickaljord 10y agoKind of worrying that the inventor of PowerShell could make such a mistake. Reminds be of when rvm used an alias for "cd", which was even worse. Making up alias for popular tools such as cd, curl or wget is always a bad idea both for security and practical reasons since it breaks many tools in non-obvious ways and can be hijacked etc. It's great though that it's being fixed. I installed PS on my ubuntu last night, it works but I don't really see the point in using it on anything but windows. Last thing I need is worry whether my scripts will run on my custom shell script as if running ubuntu didn't come with its own issues to worry about already.
- amyjess 10y ago> Making up alias for popular tools such as cd cd is a shell builtin on every single *nix shell, not an independent tool. Every shell has its own cd implementation.
- dTal 10y agoYou might also add that it's actually impossible to implement cd as a standalone tool - processes cannot change their parent's working directory.
- richardwhiuk 10y agoIt's not pretty, but you can: https://rudd-o.com/linux-and-free-software/the-shell-challenge-changing-another-process-working-directory https://rudd-o.com/linux-and-free-software/the-shell-challen...
- dTal 10y agoWell how about that. Serve me right calling something "impossible". Now what do I say? "Impossible without awful hackery"?
- iaskwhy 10y agoAre other commands also different from shell to shell? It seems like an interesting point, if true.
- snuxoll 10y agoHere's a couple of pages listing the builtins in bash: https://www.gnu.org/software/bash/manual/html_node/Shell-Builtin-Commands.html https://www.gnu.org/software/bash/manual/html_node/Shell-Bui... And zsh: http://zsh.sourceforge.net/Doc/Release/Shell-Builtin-Commands.html http://zsh.sourceforge.net/Doc/Release/Shell-Builtin-Command... Powershell doesn't really have "builtins" per-se, every cmdlet is executed in the process of the shell itself but they're all contained within loadable modules (though 2-3 modules are loaded with the shell startup by default), Invoke-WebRequest is contained within Microsoft.PowerShell.Utility for example.
- kemayo 10y agoLots of simple shell functionality is provided as builtins. See the bash manual for a list of builtins inherited from the Bourne Shell[1] and that are bash-specific[2]. Note that some of these are part of the POSIX standard, so there's not a huge amount of variance allowed between shells which are being compliant. Obviously, PowerShell doesn't adhere to this. [1] https://www.gnu.org/software/bash/manual/html_node/Bourne-Shell-Builtins.html#Bourne-Shell-Builtins https://www.gnu.org/software/bash/manual/html_node/Bourne-Sh... [2]: https://www.gnu.org/software/bash/manual/html_node/Bash-Builtins.html#Bash-Builtins https://www.gnu.org/software/bash/manual/html_node/Bash-Buil...
- akerro 10y agoI find this comment most important in all discussion: >To be honest, I don't see how this dscussion about how many people might depend on these aliases is relevant. The story as I see it is that a few years ago you decided to usurp the names of some well known tools, in the full knowledge that doing so would break those tools. You have then ignored bug reports about this for years. You really can't deny that you knew a long time ago that what you did amounted to hostile behaviour towards other people.
- kyberias 10y agoHow is that comment useful? No-one is denying anything. It's obvious that the decision to implement those aliases was incorrect. It's not like Microsoft is saying that it was correct. It's not a question of who was right or who to blame. It's a question of how to make the changes because there _are_ users that depend on those aliases.
- emodendroket 10y agoThey are also honestly pretty useful as a new user. `ls` and `dir` are more obvious things to try than `Get-ChildItem`.
- kuschku 10y agoThen maybe design new ones? "download" aka "dl" instead of curl/wget? "list" instead of ls/dir? Would also make them easier googleable
- pcwalton 10y ago> The thread goes on at length about bureaucratic requirements for the change. I don't like the characterization of the RFC process as a bureaucracy. RFC processes are more open than a pure "bazaar". In the lack of any formal, open process to make project changes, there ends up being a hidden informal "be friends with this person to get your patch merged" process, which is far less transparent.
- JeffreySnover 10y agoWhen I had no customers - I had lots of flexibility. PowerShell is now installed on many hundreds of millions of machines. With great success comes great responsibility. We can and will change things but we have to do so in a thoughtful manner. Jeffrey Snover [MSFT]