>>100 (checked)
I thought stuff like PostScript and Metafont was really cool, portable and specific processing like that is a good application of VMs, and it's funny to think there was a period where an office printer was more powerful than the machines around it.
eBPF… that sounds insane, but kind of neat. It might actually be a step towards breaking away from the limitations that Linux imposed by being destined to be a UNIX clone.
My remarks about Lisp runtimes were more about program stability (C is a plague). Trust is a social problem over a technical one, and we already let all kinds of arbitrary code run on our machines all the time, so why not go the whole nine yards?
It seems more to me that the industry is approaching the same ideas that were tried years ago in projects like Plan 9, except with none of the simplicity or consistency of those models. Apparently they could get away with disk access being as fast as a file server in 1993.
You could also have a flexible language from the beginning. Embedding an interpreter in a static language adds infinite flexibility, but how about new functionality, and even new syntax without having to change the compiler? That's how the original OOP module for Lisp was written, it was ordinary Lisp code that generated new code to expand at compile time. The simplicity and powerfulness of ordinary Lisp macros is amazing when you get down to it, and I'm wondering if any other languages have done a similar thing.
It seems Clojure is getting its traction in the industry. I've never tried it, and it seems to have its flaws and rounded edges, but if you do work in that kind of field it might be worth looking at.