This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-09-02
Channels
- # admin-announcements (21)
- # announcements (1)
- # boot (128)
- # cider (18)
- # cljs-dev (10)
- # clojure (112)
- # clojure-brasil (2)
- # clojure-italy (4)
- # clojure-japan (12)
- # clojure-russia (38)
- # clojurescript (241)
- # clojutre (1)
- # datascript (2)
- # datomic (3)
- # events (1)
- # hoplon (38)
- # jobs (1)
- # ldnclj (5)
- # melbourne (8)
- # off-topic (2)
- # om (9)
- # re-frame (13)
- # reagent (43)
- # sneer-br (24)
- # sydney (3)
and the interest in the clojure workshops has been good, so I’d imagine there’s a bunch of people who’d be keen to work with the language
we have new services to build. but the team prefer scala, because of the static type.
i also wonder, with dynamic type, how does the maintaince look like after the project grows over 3 or 4 years.
I've never understood the maintenance argument when it comes to dynamically typed languages. Any application of reasonable size should have a decent amount of tests and in a dynamically typed language you might just need a few more to verify the same thing. But I've never seen a project still be nice to work on after 3-4 years, dynamically or statically typed, they're always horrible.
And if you want to see a Clojure code base after 6 years of development here is a good example - https://github.com/ato/clojars-web