First 6 years of a life of Clojure project - Jarppe Länsiö

Lupapiste is now 6 years old Clojure project. When it started, Clojure as a language was viewed as highly controversial and risky for 'real projects'. Dynamic typing was not going to scale with more developers and with larger code-base, we were told by many.
Now, after 6 years, 120 000 end-users, 10 000 permits applied monthly, well over 40k commits made by 25 programmers over the time resulting over 125k lines of Clojure code, it's interesting to take a look how this controversial and risky language has served us.
This talk takes a look on what choices have been made, what has worked well, what has caused pains, and finally, where we are planning to evolve the code-base now as Lupapiste is going global.

[@MarkoSalmela]

An excellent presentation - one of the best I've seen. And I 've seen lot of them.

[@thomas.moerman]

Great presentation!

[@kehrin]

This talk has that Clojure energy. At the start you doubt all the people singing high praises - by the half way mark you're completely sucked in. Amazing talk 👍

[@motozirillo]

English is my primary language and I still can't speak like this. Nicely done

[@valbogda5512]

This guy is a legend.

[@kirillstepanov6551]

Great presentation. :)

[@colliderwriter7468]

The antonym of "inject" in software terms is "emit"

[@chrispaul8050]

Fantastic talk, I really enjoyed it.

[@JaihindhReddy]

For anyone interested, the data driven state machines approach seems to have been factored into a library: github.com/metosin/tilakone

[@vachi3558]

Impressive talk, when's the next one?

[@fdhenard]

Awesome talk! Are there any good libraries or frameworks for the "pattern" you used that allows one to write more pure functions in a web app? I think I've heard Eric Normand refer to this as a command pattern.

[@diegonayalazo]

Thanks!

[@smartphone6498]

Amazing talk!

[@Maaruks]

great talk

[@EcksteinNorman]

Love it ✊🏻

[@topsiterings]

you rock man.

[@softwareminimalist]

Correction - by reference data passing is your enemy, not "state". The word state is so ambiguous that everyone has their own interpretation what it means. What is the problem is the passing and changing data by reference, instead of by value.

[@fuads]

side-effects!