4 ms·

> Build systems in Java by and large fall into only 3 camps, Maven, Gradle and a very small (but loud/dedicated) Bazel camp. Contrast that to Go which is almost

by Thaxll 5y ago

> Build systems in Java by and large fall into only 3 camps, Maven, Gradle and a very small (but loud/dedicated) Bazel camp. Contrast that to Go which is almost always a huge pile of horrible Makefiles, CMake, Bazel or some other crazy homebrewed bash build system. Well Go does not need a book of 400+ pages to understand Maven.

pjmlp 5y ago
It needs one to understand Go modules and how they change across language versions.
- Thaxll 5y ago
  Go module are easy to use, compiling is even more simpler: go build .
  - pjmlp 5y ago
    If you say so, "HERO: On the Chaos When PATH Meets Modules" https://cs.nju.edu.cn/changxu/1_publications/21/ICSE21_02.pdf https://cs.nju.edu.cn/changxu/1_publications/21/ICSE21_02.pd...
    - tekknik 5y ago
      I’ve been writing go since it basically came out. Every single one of you’re comments is anecdotal so here we go. I’ve never, ever, encountered an issue compiling / building go code using modules. You also said in your first argument that you get no access to raw threads then a comment later said you do. It seems like you’re just advocating for people to use java because it’s what you’re comfortable with.
      - throwaway894345 5y ago
        Pretty sure it was a different commenter who claimed no access to raw threads, but yes, the parent user can be a bit abrasive on the subject of programming languages.
      - pjmlp 5y ago
        I am confortable with plenty of stuff, which makes me not the target audience for Go. "The key point here is our programmers are Googlers, they’re not researchers. They’re typically, fairly young, fresh out of school, probably learned Java, maybe learned C or C++, probably learned Python. They’re not capable of understanding a brilliant language but we want to use them to build good software. So, the language that we give them has to be easy for them to understand and easy to adopt." The threads comment wasn't from me.

by Thaxll 5y ago

pjmlp 5y ago

It needs one to understand Go modules and how they change across language versions.

Thaxll 5y ago
Go module are easy to use, compiling is even more simpler: go build .
- pjmlp 5y ago
  If you say so, "HERO: On the Chaos When PATH Meets Modules" https://cs.nju.edu.cn/changxu/1_publications/21/ICSE21_02.pdf https://cs.nju.edu.cn/changxu/1_publications/21/ICSE21_02.pd...
  - tekknik 5y ago
    I’ve been writing go since it basically came out. Every single one of you’re comments is anecdotal so here we go. I’ve never, ever, encountered an issue compiling / building go code using modules. You also said in your first argument that you get no access to raw threads then a comment later said you do. It seems like you’re just advocating for people to use java because it’s what you’re comfortable with.
    - throwaway894345 5y ago
      Pretty sure it was a different commenter who claimed no access to raw threads, but yes, the parent user can be a bit abrasive on the subject of programming languages.
    - pjmlp 5y ago
      I am confortable with plenty of stuff, which makes me not the target audience for Go. "The key point here is our programmers are Googlers, they’re not researchers. They’re typically, fairly young, fresh out of school, probably learned Java, maybe learned C or C++, probably learned Python. They’re not capable of understanding a brilliant language but we want to use them to build good software. So, the language that we give them has to be easy for them to understand and easy to adopt." The threads comment wasn't from me.