> Your typical architecture astronaut will take a fact like “Napster is a peer-to-peer service for downloading music” and ignore everything but the architecture, thinking it’s interesting because it’s peer to peer, completely missing the point that it’s interesting because you can type the name of a song and listen to it right away.

This sentence so succinctly summarizes the current "blockchain" craze that it's hard to believe he wrote it in 2001.

It's cute, in a "look at how I can make the language do this"/novelty way, but I don't think it's JavaScript's fault per se, as this seems similar to Java architects solving problems with "just another factory", "just another annotation", "just another bytecode generator", etc.