Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I think this is an okay idea, but the comparison to Clojure is really lacking. Why build on CL when you can build on Clojure? I get the inter-operability, but when Multi-Threading and Multi-Processing is listed under Deferred, Clojure could provide so much of that for free. On Clojure, etc.


What if you aren't interested in targeting the JVM?


Then I think the CLR would be a good starting point [1]. Or you could settle for single-threaded ClojureScript/JavaScript.

[1] https://github.com/clojure/clojure-clr


You seem to be assuming that everyone writing code should be writing code for either the JVM or CLR, which is a really weird assumption.


Because clojure is garbage?

Also, Java/JVM suck ass, why would anyone willingly work with that whole mess?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: