the programming language is janet, which looks like a lisp at a cursory glance.
why might I choose this stack with janet for a web app versus, say, Common Lisp? For instance https://lispcookbook.github.io/cl-cookbook/web.html
back
2 comments
Honestly, the easiest to approach for me was Racket's out of the box web libraries. I just never took it further than that. I've dabbled with Clojure was well with lein and luminous web framework. I just am so undecided on what Lisp I want to use for a web project. I'm so spoiled by things like Django and ASP .NET Core. I really do want to do something with Lisp beyond just simple hello world web projects just because web development is something I do often enough in my career so it makes sense to jump straight into it, but I'm not sure. Of course if I went for Common Lisp which compiler do I even go for? I liked Racket a lot because it was easy to get into due to DrRacket. I liked Clojure because it had two simple editors that are now defunct, so I'm kind of left wondering what to use if I go that route.
You mentioned Net Core, so I wanted to share this.
I started a project using Giraffe recently and love it. It’s an F# web framework that runs as a middleware in a AspNetCore app. I found F# to give me a lot of nice functional features, while also leveraging all the Dotnet ecosystem and CLR knowledge gained from my day job.
For Common Lisp, just stick to SBCL or CCL: https://common-lisp.net/implementations
I mean why use anything for anything, since another thing already exists.
Look I like common lisp just fine and have used it for serious professional work and value it for its practical strength and longevity.
It is gnarly though, and a pain in the ass sometimes, and really pretty hard to onboard people into. It's huge, and the intense focus on backwards compatibility means there are huge swathes of the language you won't use, some that possible no one should use. If you've already put the time in to learn all that then yeah sure why would you use this. But most people interested in lisps haven't spent hundreds of hours trudging through common lisp already, so maybe this is more for them.
Is there a "common lisp - the good parts" style thing that a decent percentage of users agree on?
(I've done scheme and a few others with great enjoyment and repeatedly bounced off common lisp, so I'm very much aware of the extent to which "lisp users agreeing on things" is a substantial ask, but it seemed worth a try even so ;)
> I mean why use anything for anything, since another thing already exists.
My question was to figure out WHY this might be better than the solutions that already exist, which I think is a fair question. If you're always going after the new thing without it having known / expected advantages, aren't you setting yourself up for pain?