But the only real way to be sure if something is a good idea, especially in complex distributed systems such as the web platform, is to try it out. And when you

But the only real way to be sure if something is a good idea, especially in complex distributed systems such as the web platform, is to try it out. And when you try it out at scale, standardization is very important. The alternative is to have everyone using new ActiveXObject("Microsoft.XMLHTTP") because you have a non-standardized thing that's rapidly turning out to be a good idea. The purpose of a standardization process isn't to stamp approval on good ideas; it's to ensure interoperability. Server Push was a plausible idea. It very much could have been a good idea. It turned out not to be, after we tried it in the real world for many years, but that's okay. And we know one thing for sure - the reason it didn't work wasn't that people were afraid to use a nonstandard X-Chrome-Server-Push extension.