3 ms·
That's really been the sticking point for me. As time goes on though, it becomes a little less irritating. Rich Hickey has done a really great job of managing w
by icey 19y ago
That's really been the sticking point for me. As time goes on though, it becomes a little less irritating. Rich Hickey has done a really great job of managing where the language is going so far.
Initially, I didn't even want to look at Clojure due to it living on the JVM. However, this article shows that leveraging the JVM isn't entirely terrible - sure the setup of the structures is kind of ugly, but the actual usage doesn't look bad at all.
If you reframe it as a Java FFI instead of a language living on the JVM, it's a little less... smelly.
- jrockway 19y agoI don't really care about the JVM. It's just that the code ends up looking like Java translated to Lisp. Lisp: (some-method instance) Clojure: (. instance (SomeMethod)) Yuck. But not as yucky as the real Java :)
- richhickey 19y agoClojure also supports this Lispier syntax: (.someMethod instance)
- brlewis 19y agoIs it too late for you to reframe this item that way? Your title suggests it's implementing a web server in 100 lines, when really it's creating a 100-line API for driving Java classes that implement a web server.
- icey 19y agoA) You're absolutely right. B) The title I used is the title from the blog. Aside from that, it's too late for me to make the edit.