←back to thread

175 points nateb2022 | 1 comments | | HN request time: 0s | source
Show context
Xeoncross ◴[] No.41521050[source]
> Zero dependencies

This is something seldom attempted, but I congratulate you. Go is one of a few languages that really is batteries-included. Just about anything you could need is included in the stdlib.

replies(4): >>41521157 #>>41521657 #>>41521695 #>>41521859 #
seanw444 ◴[] No.41521157[source]
One of the reasons I prefer it over something like Rust for most projects. I don't have to waste time figuring out what third-party library is the defacto standard that I should be using.
replies(1): >>41521371 #
iknowstuff ◴[] No.41521371[source]
It’s a tradeoff. Do you prefer to be stuck with bad built-in file and time APIs, or a robust ecosystem of external crates?

https://fasterthanli.me/articles/i-want-off-mr-golangs-wild-...

replies(6): >>41521608 #>>41521670 #>>41521708 #>>41521832 #>>41522235 #>>41523134 #
hu3 ◴[] No.41521608{3}[source]
So your argument is that an ecosystem of external crates which are created and maintained mostly by individual contributors is on average better than the standard library backed and dogfooded by trillion dollar company and used by other giants of the industry? Can't say I agree.

Not to mention nothing prevents anyone from using or writing their own library only for the parts that need specialization. You're free to do that and many have.

And standard libraries can be versioned and deprecated too.

replies(2): >>41523867 #>>41564060 #
1. everforward ◴[] No.41523867{4}[source]
I actually wouldn’t be surprised, if only because the standard library is so much harder to make backwards-incompatible changes to. I would generally expect that the average quality of the third party libs is lower, but the top 1% is probably better than stdlib.

Eg I don’t find the stdlib logging library particularly great; not bad, but not impressive. Ditto for the stdlib errors package before they added error wrapping