This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-02-08
Channels
- # announcements (2)
- # aws (1)
- # beginners (134)
- # calva (26)
- # cider (48)
- # cljdoc (41)
- # cljs-dev (12)
- # clojure (178)
- # clojure-brasil (1)
- # clojure-europe (16)
- # clojure-italy (30)
- # clojure-nl (13)
- # clojure-spec (118)
- # clojure-uk (81)
- # clojurescript (209)
- # community-development (77)
- # cursive (7)
- # datomic (23)
- # duct (6)
- # emacs (15)
- # events (2)
- # figwheel (13)
- # figwheel-main (18)
- # fulcro (4)
- # jackdaw (4)
- # jobs (6)
- # jobs-discuss (6)
- # kaocha (2)
- # lein-figwheel (3)
- # off-topic (4)
- # other-languages (22)
- # pathom (2)
- # pedestal (9)
- # perun (10)
- # portkey (1)
- # re-frame (41)
- # reagent (6)
- # reitit (4)
- # remote-jobs (1)
- # ring-swagger (6)
- # rum (5)
- # shadow-cljs (300)
- # sql (3)
- # test-check (6)
- # testing (7)
- # vim (1)
- # yada (9)
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”
including dependency management?
and the library ecosystem is really good
including dependency management?
I think so
literally
import (
foo ""
)
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
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