ugh okay I think I’m probably going to give up on Clojure too. to be honest there’s not much that I like about this language anyway - it feels a little bit like Racket, but doesn’t have any of the things that I like about Racket. and having to manage every project with lein is a huge pain - especially if I want to have just a few loose files that can be run independently, instead of a whole big project with a config file and everything

also, Malli’s documentation is really really bad, and Clojure’s error tracebacks are even worse than Racket’s

that is such a shame. I think I’m about ready to say “an S-expression based language is a very good idea, but there aren’t currently any nice-to-use Lisps. they’re all at least a little bad and painful to use”

I still like Fennel, though. maybe I’m just looking back at it with rose-colored glasses

you would think that Lisps would have readable error tracebacks, considering that they rely heavily on runtime errors to tell the user that something is wrong (since they can’t be statically analyzed at all (except Fennel))

but no, for some reason Lisps have some of the worst error tracebacks I’ve ever seen, which is a horrible combination with the lack of static analysis tooling