3 ms·

The problem I'm having with Lisp isn't the syntax or the language, but the ecosystem. Or rather learning about the ecosystem. There's not much information, from

The problem I'm having with Lisp isn't the syntax or the language, but the ecosystem. Or rather learning about the ecosystem. There's not much information, from what I've found, about best practices for creating a production ready application. A lot of Lisp tutorials and books extoll the virtues of the language and REPL based development but stop there. For example, I want to figure out how to use Lisp in a CI/CD environment to deploy binaries. Or learn the best practices for creating a project with multiple modules with dependencies. Edit: Is this being downvoted because I'm hijacking the thread?

slgeorge 6y ago
> There's not much information, from what I've found, about best practises for creating a production ready application I have an interest in functional (Lisp) and decided that for me Clojure was a good choice. It was designed to be used in industry so there's people out there who are using it for real applications. Although I wasn't a fan of the JVM I've learnt my bias was wrong and it's given me access to an ecosystem of libraries. As I'm more informed now I think that learning Racket, F# or one of the others would also have been fine. But, I don't regret Clojure. They're all small(ish) communities so you have to be willing to invest in the community, be willing to put together solutions from bits of information and enjoy experimenting. Whether that's the best use of your time is up to you ;-)