Clojurians Log v2

How do Clojurists experience Go from a “getting things done” perspective (apart from the fact that it’s not a sophisticated language in terms of type system, etc.)?

@borkdude I’ve found that it’s really easy to get things done in Go provided that the project is not too big

mostly because “there’s only one way to do X”

and the library ecosystem is really good

super easy to learn as well

I think so

literally

import (
  foo  "<http://github.com/author/foo|github.com/author/foo>"
)

you always have to use the same version of a library for all your projects?

i don't think there are versions. there's current source code

this used to be a problem

I guess if you want to have versions you can use a different collection of checkouts?

you usually depended on HEAD, I think

but with Go modules this has changed

yeah. i think people would fork to make their own "version"

I thought godep is the newest way https://github.com/tools/godep

sorry, dep: https://github.com/golang/dep

“The Go toolchain, as of 1.11, has (experimentally) adopted an approach that sharply diverges from dep.”

and I am wrong …

“gearing work primarily towards the development of an alternative prototype for versioning behavior in the toolchain.”

I was asking since https://github.com/candid82/joker seems like a fun project to play with

thanks for linking this