4 ms·
I'm curious as to why they didn't mention Racket—perhaps they've just never heard of it. My first programming language was Perl. After Perl came a little bit o
by ashton314 6y ago
I'm curious as to why they didn't mention Racket—perhaps they've just never heard of it.
My first programming language was Perl. After Perl came a little bit of C, but then I soon switched to Common Lisp. I wrote a lot of Common Lisp: I programed a text-based adventure game engine ala Zork entirely in CL! After reading Paul Graham's On Lisp and learning about Scheme, I took a look. My dad got me a PDF of SICP; I learned to prefer the Lisp-1 style of Scheme to the Lisp-2 style of CL.
I've done a bit of Clojure—I feel like Clojure does a better job of making data structures more ergonomic than either Scheme or CL.
I've recently started working more in Racket and I am loving it. It feels like a Scheme with a more visible, vibrant ecosystem. (Could just be me not being aware of the Scheme ecosystem—I was only 15 or so at the time I started writing Scheme.) Racket is definitely optimized for building DSLs. But I feel like the standard library is a bit better documented and easier to work with.
Just my experience though. I could be totally missing out on some great Scheme libs.
At the end of the day, Lisp in all its flavors is great, and I want to write as much of it as I can in my career.
- mumblemumble 6y agoFWIW, my first lisp was one called PLT Scheme. Most people know it as Racket nowadays. There's been a couple decades' worth of divergent evolution since then, so that it's not actually compatible with any Scheme standard anymore. At least not by default -- there's still "#lang r5rs". In any case, one could be forgiven for thinking Racket is still just another flavor of Scheme.
- peatmoss 6y agoI agree about Racket. While various lisps occupy specific niches, I feel like Racket is the lisp that checks the most boxes—especially for someone getting started and shopping around for the “right” lisp.