Yes, there's other tools that can make terminal output prettier on Linux. We all know that. But the "column" command is likely already there, on your system, waiting for you to use it. With "column...
Absolutely, the syntax and API isn’t exactly easy, but it is miles better because it’s both more familiar to other programming languages and because it is verbose.
I argue that the complaint some have about its verbosity is of little meaning, those people have just used the shell so much that they naturally remember a lot of commands, what they’re used for and their specific syntax, but for a beginner it’s difficult to string everything together, because a lot of tools are of independent origin. Regardless, Powershell should by default have quite a few aliases to the commands/functions with long names so it’s not like you can’t have the best of both worlds
I use it as a command shell regularly and the verbosity isn’t an issue at all, between aliases and tab completion.
Honestly, having used both for years, PowerShell is actually easier in many respects just due to the object pipeline and dotnet, once you get to know them well enough. Being able to just toss output into a variable and mess around with it to understand its structure and contents is huge
Always*
Shell scripting for serious tasks should crash and burn, wherever possible at least
For all that I shit talk Microsoft, Powershell does seem better suited for production tasks than bash and friends…
Powershell may be better for programming but is worse for shell tasks.
Absolutely, the syntax and API isn’t exactly easy, but it is miles better because it’s both more familiar to other programming languages and because it is verbose.
I argue that the complaint some have about its verbosity is of little meaning, those people have just used the shell so much that they naturally remember a lot of commands, what they’re used for and their specific syntax, but for a beginner it’s difficult to string everything together, because a lot of tools are of independent origin. Regardless, Powershell should by default have quite a few aliases to the commands/functions with long names so it’s not like you can’t have the best of both worlds
Yep.
I use it as a command shell regularly and the verbosity isn’t an issue at all, between aliases and tab completion.
Honestly, having used both for years, PowerShell is actually easier in many respects just due to the object pipeline and dotnet, once you get to know them well enough. Being able to just toss output into a variable and mess around with it to understand its structure and contents is huge