4 ms·

Data provenance. Now explain your side.

• zerr 10y ago
  You don't have to change #include paths in C++ (or Java imports) code when you move your project from github to bitbucket.
  • XorNot 10y ago
    Have you looked at the build system of a C++ project lately? Or a Java project? It's not like that's some super-elegant not-at-all-rolling-catastrophe of a system. Java and Node, for example, don't solve anything - to get something that builds sensibly they both entirely depend on "external service" being always available and enforcing naming (see the leftpad fiasco). C/C++ are the source of the term "dependency hell".
  • deleted 10y ago
    [deleted]
  • PopsiclePete 10y ago
    I've had to deal with CMake as well as automake/autoconf at work recently and I'll take Go's system of fetching/building any day over the Wild West that is the C/C++ eco-system.
• eternalban 10y ago
  It's an artifact of a tool. The same after-thought tool could have just dropped a mapping line in a .gotool file somewhere: $ go get whois etcd github.com/coreos/etcd But no. We need to put that in every freaking file and thus transit from information to noise.
• deleted 10y ago
  [deleted]