News for hackers. Stuff that matters.
Re:The growth of command-line options, 1979-Present by olalonde on Tuesday March 03, 2020 @11:49AM (#22476164)
> replacing them with a structured, typed, reflective API

Does this better alternative exist?

Re:The growth of command-line options, 1979-Present by seemslegit on Tuesday March 03, 2020 @11:57AM (#22476264)
No, or it wouldn't have been overdue. Microsoft powershell is probably the closest thing I can think of, which in turn is powered by the .NET/CLR type system.
Re:The growth of command-line options, 1979-Present by bigato on Wednesday March 04, 2020 @05:27PM (#22488832)
and do you find powershell to be a simpler alternative? i recently had to look into a 100 or so lines powershell script and it felt crazily hard to read. Good thing I had access to the guy who wrote it so that he just told me what it was supposed to do (he gave up explaining the script)
Re:The growth of command-line options, 1979-Present by seemslegit on Wednesday March 04, 2020 @05:36PM (#22488919)
Yes the powershell language itself is a poorly thought-out hack but using shell scripting for non-trivial tasks is a related but different problem that has to do more with a (thankfully narrowing !) skillset gap between devops/IT people and software developers. So just like a 100 or so line bash script would probably be better off written in python so would a 100 line PS script be better done in any .NET language and exposed as a cmdlet