Looks like a good primer to Go - thanks!
Smaller number of packages as compared to other ecosystems like Node.js and Ruby. However, it’s increasing.
I’ve heard this as a criticism before, but as a person who did quite a bit of Ruby, I think this isn’t a downside but is instead an upside ;)
Consider some of the most frequently downloaded Ruby gems. Lots of these are right in the Go stdlib:
json
multi_json
encoding/json
mime-types
mime
tzinfo
time
Is this just a case that Go has more batteries included than Ruby or Node.js?
Yeah, exactly! I know what you mean, I came from both Nodejs and Ruby communities to Go. And, millions of fragmented packages bit me too…
I put it there in disadvantages however I don’t think most of them as disadvantages, only that, people can may judge it that way, I’m not sure.
Looks like a good primer to Go - thanks!
I’ve heard this as a criticism before, but as a person who did quite a bit of Ruby, I think this isn’t a downside but is instead an upside ;)
Consider some of the most frequently downloaded Ruby gems. Lots of these are right in the Go stdlib:
json,multi_json->encoding/jsonmime-types->mimetzinfo->timeIs this just a case that Go has more batteries included than Ruby or Node.js?
Yeah, exactly! I know what you mean, I came from both Nodejs and Ruby communities to Go. And, millions of fragmented packages bit me too…
I put it there in disadvantages however I don’t think most of them as disadvantages, only that, people can may judge it that way, I’m not sure.