It's not really that amusing, as if these "web" people aren't intimately familiar with CS research or basic principles of programming. The web wasn't designed a

It's not really that amusing, as if these "web" people aren't intimately familiar with CS research or basic principles of programming. The web wasn't designed ahead of time for all the uses it has today, it's evolved into its current role, and often by developers forcing it to do their bidding. It's also not defined by any single entity and the standards process takes a long time. Of course something that started as an application framework would have had "subroutines" and custom components. That's no reason to deride the efforts to address that now. As for requiring JS, you are correct. A declarative custom element standard will be needed before we can have extensible HTML without script. But given that a declarative standard will be a subset, in term of power, of the imperative API, it's best to see what the most common used parts of the imperative API are before baking defining the declarative version. If you look up initial versions of MDV and web components, you'll see declarative elements in there.