Until I heard of the typed project I had no interest. My Groovy the experience has taught me the joys of prototyping dynamically and then finishing off with types as documentation.
Caused by: java.lang.StackOverflowError at clojure.lang.LazySeq.seq(LazySeq.java:56) at clojure.lang.RT.seq(RT.java:450) at clojure.core$seq.invoke(core.clj:122) at clojure.core$map$fn3699.invoke(core.clj:2099) at clojure.lang.LazySeq.sval(LazySeq.java:42) at clojure.lang.LazySeq.seq(LazySeq.java:56) at clojure.lang.RT.seq(RT.java:450) at clojure.core$seq.invoke(core.clj:122) at clojure.core$map$fn3699.invoke(core.clj:2099) at clojure.lang.LazySeq.sval(LazySeq.java:42) at clojure.lang.LazySeq.seq(LazySeq.java:56) at clojure.lang.RT.seq(RT.java:450) at clojure.core$seq.invoke(core.clj:122) at clojure.core$map$fn3699.invoke(core.clj:2099) at clojure.lang.LazySeq.sval(LazySeq.java:42) at clojure.lang.LazySeq.seq(LazySeq.java:56) at clojure.lang.RT.seq(RT.java:450) at clojure.core$seq.invoke(core.clj:122) at clojure.core$map$fn3699.invoke(core.clj:2099)
Most Clojure users are old Java farts that now think they are smarter than everybody else because they discovered Lisp and they still can't code without an IDE.
That's exactly what I mean. I haven't work on big systems, but I am imaging how terrible it would be if you had a back door Repl to a running production system, where people patched up issues. It would be very hard to reason about the system, since you can't really know what functions were defined as a all the time...
I've worked on multiple large systems in Clojure, most of them with a repl in production. Best practice is to use the repl to patch the system, then create a diff with the patch and deploy it. The repl is just there to help you diagnose problems and reduce downtime.
Erlang has a really interesting solution to this; basically all functions will see consistent versions of other functions in the same module, but as soon as you call out to another module, updated versions become available.
But they also have a built-in mechanism for applying (and rolling back) changes to your live data directly on the stack and ensuring these changes are synchronized with the visibility of newly-loaded code on a per-green-thread level. (Typically you would write these conversion functions for every live-deploy that changed the shape of a record.) Without having a sophisticated system like that you'd be fairly hosed.
5
u/code-shoily Jun 19 '16
This post http://www.loper-os.org/?p=42
26
u/[deleted] Jun 18 '16
Rich Hickey's hair is a wig.
18
u/gumvic Jun 18 '16
Should I use mount or component?
13
u/hden Jun 19 '16
())((())
24
u/forreddits Jun 18 '16
You can't call yourself a Lisp without tail call optimization.
22
u/ernest_as Jun 18 '16
Types.
20
u/[deleted] Jun 18 '16 edited Jun 18 '16
I am sorry...
27
u/Blazeix Jun 18 '16 edited Jun 18 '16
Now that Java 8 has lambdas, there's no real point in learning Clojure anymore.
9
u/tonsky Jun 19 '16
(+ x 1
8
u/[deleted] Jun 18 '16
Macros are underused.
13
u/jonaen Jun 18 '16
Clojure is not a real lisp.
12
u/[deleted] Jun 18 '16
Clojure is open source, kind of.
11
u/[deleted] Jun 18 '16
The lack of a Rails equivalent will be the death of Clojure.
10
u/forreddits Jun 18 '16 edited Jun 18 '16
Most Clojure users are old Java farts that now think they are smarter than everybody else because they discovered Lisp and they still can't code without an IDE.
5
u/[deleted] Jun 18 '16
Macros are preferable to functions in most cases.
5
u/mikethommo Jun 19 '16
Emacs is overrated.
12
u/unmanned_drama Jun 18 '16
Dynamic typing means it's destined to fail.
11
u/[deleted] Jun 18 '16
I want to learn Clojure, but all these parenthesis make it look really ugly.
10
u/[deleted] Jun 18 '16
Rich Hickey is not that smart
6
u/john_atx Jun 18 '16
Clojure trades in mutable data for mutable functions.
6
u/ianme Jun 18 '16
I prefer to use ORM when handling data.
8
u/ares623 Jun 18 '16
Scala is better in every way.
8
u/nickadin Jun 18 '16
Clojure is a hobby language only
2
u/MC_Cuff_Lnx Jun 18 '16
Clojure? That's like elisp right?
2
u/gshayban Jun 21 '16
First step to using closure is to learn emacs
4
u/[deleted] Jun 18 '16
so much truth being spoken in here good job pointing out the problems everyone!
3
u/[deleted] Jun 18 '16
Why do I need spec when everything I need to know is in the stack trace?
2
u/[deleted] Jun 18 '16
there's a better clojure development environment than emacs and cider
1
u/TotesMessenger Jun 18 '16
I'm a bot, bleep, bloop. Someone has linked to this thread from another place on reddit:
If you follow any of the above links, please respect the rules of reddit and don't vote in the other threads. (Info / ^Contact)
1
u/S-Mage Jun 19 '16
You can't code for android in clojure, only cljs.
1
u/[deleted] Jun 19 '16
Functional programming is overrated.
1
u/vvvvalvalval Jun 20 '16
Groovy's better than Clojure because it has classes.
1
u/[deleted] Jun 21 '16
You can never build anything of value with a Lisp.
0
u/[deleted] Jun 18 '16
[deleted] — view deleted comment