> This made me realize that Go was always promoted as "do not use frameworks, do not use libraries, use standard library, everything you need is in there".
I've been writing Go since 2012 and have no idea where you picked up this sentiment. The stdlib is there to give you many useful capabilities but it's focus has always been on correctness and flexibility rather than performance.
If performance is your concern, it's always been recommended to reach for other libraries that share that focus.
There's plenty to dislike about the direction Go is moving but stdlib performance isn't one of them. Just find a package that suits you better.
i have been coding exclusively in Go for 5-6 years and it was never not the case. So you might have some remaining bias if you started in 2012 when things might have been different.
I would like to see those benchmarks that are being conducted. Care to share a link?
Regardless, there is definitely acknowledgement within the community that some parts of the standard library could use a rethink based on lessons learned in the past decade.
I did not share any links on purpose because then it would turn into a discussion about the methods the tests were done and it would detract from the main point. Anyone interested in this can look up videos or articles on this topic.
> This made me realize that Go was always promoted as "do not use frameworks, do not use libraries, use standard library, everything you need is in there".
I've been writing Go since 2012 and have no idea where you picked up this sentiment. The stdlib is there to give you many useful capabilities but it's focus has always been on correctness and flexibility rather than performance.
If performance is your concern, it's always been recommended to reach for other libraries that share that focus.
There's plenty to dislike about the direction Go is moving but stdlib performance isn't one of them. Just find a package that suits you better.
> I've been writing Go since 2012 and have no idea where you picked up this sentiment.
It is taken to extremes on the Gophers Slack.
true. but slack is also quite dead. discord seems to be more active.
i have been coding exclusively in Go for 5-6 years and it was never not the case. So you might have some remaining bias if you started in 2012 when things might have been different.
I would like to see those benchmarks that are being conducted. Care to share a link?
Regardless, there is definitely acknowledgement within the community that some parts of the standard library could use a rethink based on lessons learned in the past decade.
There is already some effort towards this with encoding/json/v2: https://github.com/go-json-experiment/json
I did not share any links on purpose because then it would turn into a discussion about the methods the tests were done and it would detract from the main point. Anyone interested in this can look up videos or articles on this topic.
> the only true competitor is c# due to having runtime and GC, which is sparsely tested so not relevant to the conversation.
Could you expand on this?