Re:What was the point of [ “x$var” = “xval” ]?
by TeMPOraL on Monday April 12, 2021 @07:17AM
(#26778120)
Seconding PowerShell. Or some future development that files off the rough edges, but otherwise follows the same sane principle of piping objects instead of unstructured text :).
[ Parent
| on HN ]
Re:What was the point of [ “x$var” = “xval” ]?
by michaelcampbell on Monday April 12, 2021 @09:03AM
(#26778911)
So. Much. Typing. though.
Re:What was the point of [ “x$var” = “xval” ]?
by netmare on Monday April 12, 2021 @11:21AM
(#26780363)
Command/type aliases and autocompletion make this a non-issue on the console and advanced code editors. Personally, I don't mind the verbosity even when using plain editors, like Notepad2, my text/script editor of choice.
Extra-long command names and deeply namespaced .Net types can be a chore both to read and write, but I find the *nix tools way too cryptic. Never could get used to them, but then again, I've been on DOS/Windows all my life since the 90s.
To be honest, I'd occasionally get frustrated and think about switching to Linux. However, Python and PowerShell are the two things that have kept me on Windows. The fact that they are both open-source and cross-platform is just the cherry on top.