4 ms·

I've been using Clojure for about a week and out of the issues mentioned in the article, I find the stack trace and import issues the most annoying. Also, since

I've been using Clojure for about a week and out of the issues mentioned in the article, I find the stack trace and import issues the most annoying. Also, since it's built on the Java ecosystem, clojure seems to have inherited all the config bullshit which is a big reason I left that world years ago. I guess I thought those issues would have improved over the past 7 years, but it appears not.

swannodette 17y ago
import thing is something you have to learn. It's well thought out and fine grained. the config bullshit - yes. There are various community efforts in progress to help on this front. that said, once you've built your first web app in Clojure (and Compojure) and debugged/updated it via a remote REPL à la Paul Graham, the pain points become less ... painful.
- torr 17y ago
  What's the typical workflow for this look like? That is, if you're making changes to the code live, and you're trying this and that in the REPL to fix things; once you get it working, how do you then get those changes out and then into your source code repository?