2 ms·
> The reason you get twelve replies is because PowerShell is the answer ...to a question not asked. No, really, I want Linux tools, and don't want PowerShell.
by JoshTriplett 8y ago
> The reason you get twelve replies is because PowerShell is the answer
...to a question not asked. No, really, I want Linux tools, and don't want PowerShell. When I want more than a shell, I want a real programming language, not a more powerful shell.
I appreciate that some people like PowerShell. But the answer to "no, not PowerShell" is not "let me tell you about why you want PowerShell anyway, you just don't understand".
> That said there’s a great case to be made for familiarity and experience
And simplicity.
Here's a closely related example. Back when there was more than one competing distributed version control system, there was "tla" (a predecessor to baz, which was a predecessor to bzr). tla had commands like "init-tree" (not "init"), "file-diffs" (not "diff"), "apply-changeset" (not "apply"), "make-branch" (not "branch"), a dozen commands for logs (not "log"), and so on. Perforce has similar problems.
And PowerShell has "Expand-Archive" (not "unzip" or "tar"), "Invoke-WebRequest" (not "wget" or "curl"), "Get-Unique" (aliased as "gu" but not "uniq" or "unique"), and so on. Brevity is a virtue in a tool used so frequently, and brevity is not lack of clarity. Unnecessary verbosity is often an obfuscation.