Hacker News new | past | comments | ask | show | jobs | submit login

> However Go has 19 years on Python

Go explicitly dismisses everything learned by the programming language (and tooling) community at large because its authors "know better".

There really isn't much to say about Go anymore in my opinion, other than answering the title of this post with "Don't".




What tooling are they dismissing? Default tooling is pretty much inexistant in other languages.


>What tooling are they dismissing?

A proper package manager, like cargo, npm, pip, composer, maven and the like, for one.


Except Cargo, none of these are default toolings and were made by the community.


Irrelevant, as I didn't say the Go team should build a package manager, just that Go lacks one.

And I mean a dominant one -- there's a few attempts for Golang. Default doesn't have to mean "core-team built". All the package managers I've mentioned are de-facto standards for their respective languages.


Irrelevant


As to what? Or you just wanted to say that?

Surely not the the discussion here, which is about "how to start a Go project in 2018" -- or the subthread, about the kind of tooling Go lacks.


Just wanted to say that


maven has plugin which allows to build golang projects and organize work with packages and cvs




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: