#clojure

23 posts · Last used 9h

I've recently been working with a large, legacy codebase written in an older language with very limited capabilities. It's in this case that I've found LLMs to be extraordinarily useful in handling the tedious work involved. But it's also got me thinking about why I haven't found the need to generate #Clojure code, and I suspect it's because by the time I've figured out what I want, it's easier to write it in Clojure than to explain it in English. 1/2
10
1
2
1
This port of the CL condition system to Jolt looks interesting. Haven't been through it in detail, but the write-up on it, at a quick glance, looks thorough. https://reddit.com/r/Clojure/comments/1wr299y/cl_conditions_and_restarts_in_jolt/ (I don't know what Jolt is either, but I guess a Clojure library or DSL. since it's on their subreddit.) EDIT: I see the Foralero package, which I did not look up because the name did not immediately suggest conditions, is probably the real source. I'm not a Clojure user so just stumbled into this by chance. https://github.com/IGJoshua/farolero #CommonLisp #lisp #ConditionHandling #ErrorHandling #ErrorSystem #clojure
5
0
4
0
Replying to

@screwlisp@gamerplus.org @ramin_hal9001@fe.disroot.org "The great thing about #Lisp is that it has extremely simple syntax"

... except, of course, for #CommonLisp which is a complete baroque mess.

Of course, it's largely a complete baroque mess because reader macros, and reader macros are useful shorthand, but #$(words)? Really?

And noted also that #Clojure has its own baroquery hard-coded into its reader (#{:a :b [:c @D@mastodon.scot]}, anyone?), which is arguably worse, but...

This might as well be #Perl.

4
5
0
0