The thing about lisp, it’s that it’s fairly expressive. You only need a few foundational libraries (mostly algorithms) and it’s very easy to build on the rest. In something like Python, or Go, once you define a conceptual model in a library, you need another library for the glue code to bind it to another ecosystem. In Lisp, almost everything is using the basic list, alist, and plist,…

So you design from the core logic and write shim to external dependencies. Instead of bringing deps from the get go.

> You only need a few foundational libraries (mostly algorithms) and it’s very easy to build on the rest.

Yeah but i don’t want to. Let’s say i need to connect to rds using iam authentication.

I don’t want to write code for that, i want to use a library.

I don’t want a library that works with chicken scheme but not on sbcl and maybe on cmucl.

I know i can, i don’t want to. I want to reuse code written and maintained by other people.

> I don’t want to write code for that, i want to use a library

All the people that had that need wrote code for that. And I guess they don’t want to do unpaid work by providing a full fledged library.

> I know i can, i don’t want to. I want to reuse code written and maintained by other people.

Then I guess Lisp is not for you.

> Then I guess Lisp is not for you.

Aaand back to square one. Go tell to most of the industry and you get the lisp curse.

Thank you for proving me correct.

Given this elitist mindset of the lisp community, no wonder there’s a thing called “lisp curse”.