News for hackers. Stuff that matters.
Re:Scala vs Go by mi100hael on Tuesday February 14, 2017 @12:03PM (#13644999)
> For all my non-trival projects I always fork all my dependencies into their own repos

That sounds absolutely terrible. Even worse than having to track down & install libraries and headers for C projects. At least in the case of those libraries, you can enforce a particular version using autoconf or whatever. Vendoring source code for dependencies (especially in separate repos) is fragile and a pain for anyone else to track down when jumping in to your existing project.

Re:Scala vs Go by voidlogic on Tuesday February 14, 2017 @01:40PM (#13645940)
How so? The project just includes a script that git clones the forks into your Go workspace for the project /foobar/src....
Re:Scala vs Go by mi100hael on Tuesday February 14, 2017 @10:23PM (#13649416)
And then you have to maintain a bunch of ad hoc shell scripts separate from your actual build process. Like I said: fragile and a pain.
Re:Scala vs Go by voidlogic on Tuesday February 14, 2017 @11:07PM (#13649606)
Besides a shell script with a "for each repo. git clone", there is no build process (besides running the go build command)...
Re:Scala vs Go by lowmagnet on Wednesday February 15, 2017 @12:11PM (#13653510)
And of course the fact you're forked off means you can update at your own pace and not have to take someone's ticket to "fix" a "broken" build. While I don't do this forking, it can help control churn, especially in projects with lots of deps.