News for hackers. Stuff that matters.

A comment on Exploring CLI Best Practices. Parent comment

Re:Exploring CLI Best Practices by yannis on Tuesday October 11, 2016 @06:40PM (#12689107)
Go has been a game changer for me also. There is also a very good package https://github.com/spf13/cobra that can make the development of complex CLIs easier.
[ Parent | on HN ]
Re:Exploring CLI Best Practices by aikah on Tuesday October 11, 2016 @07:23PM (#12689323)
Go default flag package is pure garbage though. That's a fact. However, Go cross compilation makes it easy to develop multi-os CLI tools. The downside is the size of the executable, it's easy to reach the 50MB bar with Go binaries.
[ Parent | on HN ]
Re:Exploring CLI Best Practices by skj on Tuesday October 11, 2016 @09:16PM (#12689765)
Yes. The default "flag" package is trash. I like the Go team a lot, and I think they did a great job with many things, but it seems to me like they just said, "meh, get something that can work, usability is not something that matters."
[ Parent | on HN ]
Re:Exploring CLI Best Practices by ptman on Wednesday October 12, 2016 @03:24AM (#12690965)
consider the history, it probably makes sense if you're used to research unix and plan9
[ Parent | on HN ]
Re:Exploring CLI Best Practices by integrii on Thursday October 13, 2016 @03:21PM (#12703329)
How exactly do you create a program in go that compiles to a 50mb exe?

Why is the flags package trash?

[ Parent | on HN ]