[Avamander]

It's somewhat similar to H2 Push, which had similar justifications about adoption and interest. When frameworks finally started supporting it to some extent Google expressed their wish to kill the feature, that instantly dissuaded most developers finishing their implementations or from even considering it.

(Not to mention the fact that the developer tooling for H2 Push was terrible to say the least for a long time)

To me it seems Chromium/Google are somewhat out of touch on how slow the web and adoption of new things happens.

In this case, it was also behind an experimental flag, I don't know how the f** they expect people to show interest if it's practically not usable on the web.