Thread 105724692 - /g/ [Archived: 704 hours ago]

Anonymous
6/27/2025, 7:40:45 PM No.105724692
1748445352960270
1748445352960270
md5: 8b09e5395a4a4e6a96f6a76d44e5080b🔍
If Lisp is readable, why do Lispers throw temper tantrums when a 5 line function doesn't have a 10 line comment documenting everything it does? I thought your language was readable, Lispbros? In a normal language, documentation only exists for people who can't read code, since it's always less descriptive and less readable than code. Can Lispers not read their own code?
Replies: >>105725485
Anonymous
6/27/2025, 7:43:43 PM No.105724729
I've literally never seen this unless you're talking about a sophisticated macro. You sound like you have a screw loose.
Replies: >>105724823 >>105725545
Anonymous
6/27/2025, 7:50:21 PM No.105724823
>>105724729
Browse the lisp thread more often I guess
Replies: >>105725456 >>105725624
Anonymous
6/27/2025, 8:46:04 PM No.105725435
you comment what the code cannot say
Lisp code has too few comments if anything
Anonymous
6/27/2025, 8:47:42 PM No.105725456
>>105724823
No, you browse my fucking nuts you whore
Anonymous
6/27/2025, 8:50:17 PM No.105725485
>>105724692 (OP)
lisp is readable
but lisp code also has a lot of newly defined macros with which one may be entirely unfamiliar. many lispy types don't want to admit it but many code bases end up with almost a different vocabulary so to say
Replies: >>105725545
Anonymous
6/27/2025, 8:55:21 PM No.105725545
>>105724729
>>105725485
Right, the only readability problems with s-expr languages are all the user-defined DSL macros. It could have been more readable if every Lisp had Scheme syntax macros instead of going for direct AST manipulation.
Anonymous
6/27/2025, 9:02:28 PM No.105725624
>>105724823
I use Lisp and have never encountered this. I'll nearly always comment even short macros unless they're common tools I'd expect someone to know or be able to figure out.