Why isn’t Lisp more widely used in web development?
You’d love to make a site in Racket, the hottest Lisp out there. The Racket developers have built up a truly impressive system that’s a real pleasure to use.
All the ingredients appear to be there:
Built in web-server? Check.
High-quality, thorough documentation? Check and check.
A Lisp that feels like it comes from the future? Oh yeah.
But there’s precious little guidance out there on how to make real-world web sites with the Racket web server.
Sure, the official documentation contains a handful of simple examples. They’re a good start. But you’re not sure how to move from them to making a more complex site. There’s a big gap.
Maybe you start to suspect that Racket’s HTTP server is just a fancy toy.
Maybe you’ve even given up on the idea of hacking the web in Lisp.
That would be a real shame, because the Racket web server—while fairly lean compared with other web frameworks out there—is powerful and flexible.
And when you combine Racket’s HTTP server with the cutting-edge features of Racket, we’re talking about a system that web developers can drool over.
Even if you’re new to the web, Racket’s direct approach gives you a delightful way to dip your toes in without getting bogged down in a bazillion different frameworks and dependencies.
Server: Racket is an ebook all about real-world web development with the Racket’s built-in HTTP server.
I’m working on a new book called A Short Introduction to Web Programming with Continuations in Racket. It focused on a killer feature—continuations—provided by the Racket web server. If you want to dig in to a feature that makes Racket really special for the web, take a look. Server: Racket talks about traditional URL-based dispatching; it deliberately does not talk about continuations.
We will build take on the battery of problems faced by web developers who want to hack the web in Racket. You’ll find out how to solve problems that the official Racket documentation doesn’t talk about (not in detail, anyway, and not in any full-length tutorial way).
In 184 pages, we’ll dig in to these web development topics and see how to deal with them in Racket:
Working with HTTP requests and responses entirely within Racket: no external systems, and using only modules that come standard with Racket.
request? → response?Where we begin to connect to specialized systems running outside of Racket and use specialized packages that aren’t included in a standard Racket installation.
The ebook is in PDF format, with Racket starter code—fully-functioning mini-sites—illustrating how these topics can be tackled with Racket, for nearly every chapter.
Server: Racket was essential reading as I built my first e-commerce site from scratch with Racket. It’s a terrific, practical book with lots of useful ideas and examples.
(Matthew Butterick, creator of Pollen and author of Beautiful Racket, Practical Typography, and Typography for Lawyers, talking about his Racket-powered site mbtype.com)
Chapter 1, In the beginning there was request? → response?, can be viewed here.
Use the button below to purchase the ebook: