this post was submitted on 24 Nov 2023
1 points (100.0% liked)

Lisp

53 readers
3 users here now

founded 1 year ago
MODERATORS
 

I keep flipping between Clojure and CL. I like functional programming, so I really like the workflow of Clojure, but the more-interactive nature of CL is incredibly appealing and I like that it doesn't put so many constraints on you. I love how you can inspect everything and dig into the core of the language so easily and the interactive debugger is insanely cool.

But I just find it so painful to use, all the functions have strange names, docs are shaky especially for libraries, and I just keep bouncing off. I am going to try Advent of Code in CL this year, but I always get tied up in knots with the data manipulation, especially how you seemingly need to use the loop macro for basically everything since there aren't that many data structure manipulation methods in the standard library. Hashes are also pretty awkward to work with compared to Java Maps or clojure maps.

Also, I can't shake the feeling that doing all my data manipulation with linked lists is horribly slow, especially since they aren't lazily evaluated.

ASDF and the package system is like no other language I've ever used, which always ties me in knots, too.

Does anyone have any tips? Is there something I'm missing regarding data manipulation, or is it more a matter of breaking through the pain barrier with practice?

you are viewing a single comment's thread
view the rest of the comments
[–] unixlisp@alien.top 1 points 11 months ago (5 children)

"all the functions have strange names", very strange. Most names in CL standard are self-explanatory, such as DEF*, DEFINE-, MAKE-. Others have well-known history or legends or rules. Few are difficult, such as PRIN1 (still have meaning, think about PRIN2)

[–] noogai03@alien.top 1 points 11 months ago (4 children)

"progn" is a good example. This has far more sensible names in other Lisps. But I'm mostly talking about data structure access methods. They are so inconsistent - at lead the access library improves on this though.

Well known histories/legends/rules don't count, I'm talking about new developer experience. But I get your point, they have a sort of consistency to them

[–] unixlisp@alien.top 1 points 11 months ago

PROG1, PROG2, ..., PROGN very ruleful. N reminds you returning the last value. On the other hand, PROG means "Program Feature". PROGN is really a good name.

"They are so inconsistent". Different data structures have different operations. Specific operators are accurate and efficient. The costs are that you have to remember/command all these operators. A similarity is the equality operator. EQUALP is most generic. But you mostly use EQ, EQL, CHAR=, STRING=, etc. for specific objects.

load more comments (3 replies)
load more comments (3 replies)