2 ms·

I agree with the complaints about project structure (GOPATH), difficulty importing third-party modules/packages, upper-case/lower-case public/private scoping no

I agree with the complaints about project structure (GOPATH), difficulty importing third-party modules/packages, upper-case/lower-case public/private scoping not ideal... But I think it's a very good, flexible language on the whole and I think its approach to OOP and pointers is really good (even though it's different from most other OO languages). Unlike some of the comments, I think it's actually not too verbose considering the flexibility it offers (it's much less verbose than C++). That said, for building web applications, I still prefer Node.js.

ovao 10y ago
I'm curious: what is it you don't like about importing packages in Go? With go get and goimports editor integration, I find third-party package integration pretty easy. If it's a question of versioning or package.json-style dependency management, I agree that Go still has some significant pain points that haven't been fully addressed directly.
- parenthephobia 10y ago
  Not the GP, but I note it's difficult to, say, take some code which uses package xyz and substitute the source-compatible package abc without editing every file. e.g. Try compiling a large project with a custom version of 'os' swapped in. (e.g. To add tracing, or simulate random I/O failures.) Some package management systems can decouple what packages are called inside the code from what they're called outside.