News for hackers. Stuff that matters.

A comment on Golang’s most important feature is invisible. Parent comment

Re:Golang’s most important feature is invisible by TheDong on Sunday January 23, 2022 @12:26AM (#30043865)
They exist (fasthttp and fastjson for example), but no one actually uses them.

I should have written "no one wants to use third-party versions of these packages", and I don't think that small semantic issue changes my comment meaningfully.

Do you take issue with the way I'm presenting the go ecosystem other than that small pedantic point?

[ Parent | on HN ]
Re:Golang’s most important feature is invisible by konart on Sunday January 23, 2022 @04:39AM (#30044877)
>but no one actually uses them.

The two companies I worked in (and still work as of now) both were using fasthttp and non-stdlib json parser (jsoniter and jstream to be exact).

In fact in my experience - nobody uses stdlib implementations outside of projects were stdlib is actually enough (and that's a lot of projects actually) and temp\prototype projects.

[ Parent | on HN ]
Re:Golang’s most important feature is invisible by riwsky on Sunday January 23, 2022 @03:53AM (#30044682)
People do use them, though. Look through the fastjson dependents on GitHub[1] and you'll find serious projects from the Kubernetes special interest groups and various blockchains. Heck; elastic even built their own for beats[2]. There's no big philosophy difference here. Most go programmers choose encoding/json over fastjson for the same reason most Jackson programmers choose databind over streaming: it's a simpler API.

[1]: https://github.com/valyala/fastjson/network/dependents?depen... [2]: https://github.com/elastic/beats

[ Parent | on HN ]
Re:Golang’s most important feature is invisible by lelanthran on Sunday January 23, 2022 @06:06AM (#30045294)
> I should have written "no one wants to use third-party versions of these packages", and I don't think that small semantic issue changes my comment meaningfully.

No, they don't. But if performance becomes an issue, they can!

> Do you take issue with the way I'm presenting the go ecosystem other than that small pedantic point?

Well, yes, a little. The comparison you're making is presented as "The Java ecosystem has a better outcome than the Go ecosystem". TBH, that's only for performance, and is basically a non-issue if the performance poor.

IOW, you're doing the ultimate in premature optimisation. In the real world, people who run into performance problems will a) run into them sooner with Java, and b) solve them the same way in Go.

[ Parent | on HN ]
Re:Golang’s most important feature is invisible by neodon on Sunday January 23, 2022 @04:12AM (#30044749)
https://github.com/valyala/fasthttp

It has 16.8k stars. Is that good?

[ Parent | on HN ]