News for hackers. Stuff that matters.

A comment on What's Coming in Go 1.15. Parent comment

Re:What's Coming in Go 1.15 by benhoyt on Wednesday May 13, 2020 @01:48AM (#23163858)
These days when I see a fast, reliable CLI tool I think "this has got to be written in Go" and a lot of the time they are. Some examples: the new GitHub CLI, Docker, Hashicorp tools, ngrok (though v2 is not open source), Caddy, the list is quite long. I can't vouch for the quality of that code, but I suspect some of those projects are good starting points. And I've found the Go standard library source to be really helpful (and generally fairly easy to understand).
[ Parent | on HN ]
Re:What's Coming in Go 1.15 by megameter on Wednesday May 13, 2020 @03:20AM (#23164352)
Speaking from some experience, Go is probably the best option these days at "do one thing well" command line tools - the mix of library support, native binaries, and the simple, stable language make it a good fit for a weekend project that opens files, munges strings and pushes them over standard protocols.

When Go has to support a large application that defines a platform in itself, the downsides of the language rise to the forefront, but that level of expression usually isn't entailed in a Unix-style CLI tool.

(Rust also has more potential for performance scaling in this space, but with the "if you have the time for that" kind of caveat.)

[ Parent | on HN ]
Re:What's Coming in Go 1.15 by CogitoCogito on Thursday May 14, 2020 @06:58AM (#23177986)
One thing I hate is that the go flags package sorts the options by default. Ordering options in a thoughtful way is definitely a plus in an api. I know there are (not very intuitive) ways to override this, but I just can't understand why they would make such a bizarre choice even given their penchant for being opinionated.

edit: Now that I read this over, this complaint seems a bit misplaced in this thread, but I guess I'll leave it due to its sort of relation to cli programs in go.

[ Parent | on HN ]
Re:What's Coming in Go 1.15 by majewsky on Wednesday May 13, 2020 @05:37AM (#23165126)
> Rust also has more potential for performance scaling in this space, but with the "if you have the time for that" kind of caveat.

When you have a CLI for some network-based service, the network latency is going to be magnitudes larger than the performance differences between Go and Rust anyway. (Or at least in 99% of cases.)

[ Parent | on HN ]
Re:What's Coming in Go 1.15 by tonto on Wednesday May 13, 2020 @12:40PM (#23168732)
some suggestions are that in the future, the I/O latency is going to get very low, network speeds very fast, etc.

[0] https://www.youtube.com/watch?v=SM3PhGGllL0&feature=youtu.be [1] https://www.ece.rice.edu/~willmann/teng_nics_overview.html

[ Parent | on HN ]
Re:What's Coming in Go 1.15 by majewsky on Wednesday May 13, 2020 @03:16PM (#23170628)
Unless that 10-gig NIC messes with the speed of light, I don't see it reducing the RTT between me and some server in the US by any significant amount.
[ Parent | on HN ]
Re:What's Coming in Go 1.15 by akoncius on Wednesday May 13, 2020 @09:24AM (#23166631)
not sure about docker/kubernetes. I've read somewhere that after investigation of source code there were conclusions that source code is not using good practices, a lot of duplication of code and so on thus making conclusion that project has some risks in technical debt or something like that. Would not be good to learn from project which is not well written :)
[ Parent | on HN ]