News for hackers. Stuff that matters.
Re:From Rails to Clojure, Then to Java, Then Back to Rails by ken on Wednesday March 21, 2018 @01:12PM (#16640198)
It has much more syntax than any other Lisp I know, and it seems alien even coming from Common Lisp. In addition to the usual (list) and 'quote and `backtick and :keyword and ;comment, it has [vector] and {map} and #{set} and #(function) and @deref and #"regex" and ^metadata and #?(:conditional) and ...

(Yes, several of those are implemented as reader macros. I don't see how that would make them any easier to learn than the same feature implemented as "syntax".)

That's not a knock against it. I think Clojure is the best general-purpose language today, but we've come a long way in the past few decades. Lisp is no longer a language whose implementation fits on a blackboard (and everyone extends it in their own way). We've discovered a bunch of common functionality that almost all programs need, and pushed it up into the stdlib and language.

Re:From Rails to Clojure, Then to Java, Then Back to Rails by dragandj on Wednesday March 21, 2018 @03:35PM (#16641529)
It's only optional though. You can use (list 1 2 3), (vector 1 2 3), (hash-map 1 2 3 4), and (fn [x] (inc x)).
Re:From Rails to Clojure, Then to Java, Then Back to Rails by ken on Thursday March 22, 2018 @11:00AM (#16649192)
I wouldn't say features like [vector] are optional alternatives to (vector), if you can't write even the simplest function without using the [vector] syntax.
Re:From Rails to Clojure, Then to Java, Then Back to Rails by tytytytytytytyt on Wednesday March 21, 2018 @05:12PM (#16642468)
That's not relevant here. Most code uses those things, no??
Re:From Rails to Clojure, Then to Java, Then Back to Rails by solaxun on Wednesday March 21, 2018 @02:13PM (#16640866)
True, but i don't have to remember 5 different map implementations either :)