I’ve been playing with Wisp all week.
I like it a lot. I don’t think I’m going to use it for anything other than toy and personal projects, but I am 100% going to use it.
It is a lot like ClojureScript—just as ClojureScript’s heritage in the JVM is very strong and noticeable, Wisp’s birth from JavaScript is right on the surface.
A previous version of wisp’s README suggested that you think of it as
markdown for JavaScript programming
That seems 100% true. Wisp is less a new language, and more a different way of writing plain old JavaScript.
I really enjoy writing a Lisp, and am excited to do it more. I’ve been fascinated by Lisps for a while now, and have been playing with them more and more. I’ve sunk a lot of time into Common Lisp over the last 2 years, but I am finding myself drawn more to ClojureScript and little things like Wisp.
While I really like Common Lisp I’ve struggled to find my footing with its tooling. A major advantage of Wisp is that it is just JavaScript, so I’m able to use all the packages and tools that I’m already used to, but in a new way.
Even when I’m not writing a Lisp, I think getting into Lisps has made me a better programmer (at least a better functional programmer). I love the granularity of functional programming. When I’m doing it, it feels more like preparing a meal than it does orchestrating a machine that I’m only able to look at sideways. Ingredients, prepared and combined in different ways, leading to different results.
Published