I've worked on a couple large Web-involved projects that would not have been viable, had they not used a Lisp (one Scheme, one CL). (The Scheme one, some advanced ancient astronaut before me had single-handedly made an architecture that did every complicated thing needed, and I'd say wouldn't have been viable to do in a non-Lisp.)
It's easier in the last few years to see why startups aren't using a Lisp, despite PG's early advocacy of that -- they want a very polished-looking Web/app frontend, and everyone is pushing you to buy into their frameworks and SDKs for that.
But I'd still like to see some students who played with Racket/Scheme/CL in college spin out to do a startup with a Lisp for prototyping/beta, and once they have real funding (when they should probably be rewriting prototype code in any case, or even pivoting) decide whether to keep going with a Lisp. (If they keep going with a Lisp, a bonus is that they have special access to a disproportionately high-skilled labor pool, like in other niches that attract nerdy enthusiasts.)
It's easier in the last few years to see why startups aren't using a Lisp, despite PG's early advocacy of that -- they want a very polished-looking Web/app frontend, and everyone is pushing you to buy into their frameworks and SDKs for that.
But I'd still like to see some students who played with Racket/Scheme/CL in college spin out to do a startup with a Lisp for prototyping/beta, and once they have real funding (when they should probably be rewriting prototype code in any case, or even pivoting) decide whether to keep going with a Lisp. (If they keep going with a Lisp, a bonus is that they have special access to a disproportionately high-skilled labor pool, like in other niches that attract nerdy enthusiasts.)