Re:How to write Common Lisp in 2017 – an initiation manual
by pnathan on Tuesday March 28, 2017 @09:55PM
(#13982661)
The CL community tends to expect you to read the source. You're not just a user, you're a programmer too - and quite possibly of the library you want to use.
It's an interesting dynamic, very alien to modern computing modalities.
Re:How to write Common Lisp in 2017 – an initiation manual
by jabl on Wednesday March 29, 2017 @02:46AM
(#13983966)
Sometimes I get the feeling that the lack of CL libraries is somewhat self-imposed. "We don't need no stinking libraries. Since CL is so AWESOME, a competent CL programmer can reimplement whatever he needs in a fraction of the time that programmers using a lesser language would need even with the help of ready-made libraries". See "smug Lisp weenie".
Not saying that the above is actually factually true; certainly quicklisp has done a lot to make 3rd party libraries a lot more approachable.
Re:How to write Common Lisp in 2017 – an initiation manual
by wruza on Wednesday March 29, 2017 @10:13AM
(#13986354)
I'm not an experienced web/http developer, but it [1] seems pretty understandable and even contains "Your own webserver (the easy teen-age New York version)" section for those who don't care, give them teh routez guys. define-easy-handler serves exactly that purpose.
From what I'm able to recall from my childhood, all docs were like that.
[1] http://weitz.de/hunchentoot/
I love CL and the idea of Lisp in general, but its modern unpopularity makes it hard to ask questions (because chances are you won't get a response any time soon) and the library situation is a real downer.