Not sure what you&#x27;re ranting about here. What closed protocols &#x2F; technologies are vendors creating that pose a risk?<p>On the contrary over the last few years we&#x27;ve seen vendors start to converge on web standards (HTML, CSS, JS) [2].<p>We&#x27;ve seen the development of crucial technologies for rich multimedia &#x2F; interactivity on web apps like websockets (RFC 6455 [3]) and WebRTC [4]. Things like an open browser automation protocol is helping devs build cross-browser apps [5].<p>Also, 1) we&#x27;re up to RFC 7639 in the official list [1], so that&#x27;s about 2000 RFCs since the one you mentioned in your article. 2) RSS is not a protocol 3) vendors <i>are</i> building completely open source tools (e.g. Facebook &amp; Google with React &amp; Angular.js) 4) &quot;companies now deliver one half of their application and some custom protocol over HTTP and never mind inter-operability with other services or playing nice&quot;, really confused about this, do you have any examples? 5) Are you suggesting that HTTP is transport layer? Because it&#x27;s not [6]<p><pre><code>   [1] http:&#x2F;&#x2F;www.ietf.org&#x2F;download&#x2F;rfc-index.txt
   [2] http:&#x2F;&#x2F;caniuse.com&#x2F;
   [3] https:&#x2F;&#x2F;tools.ietf.org&#x2F;html&#x2F;rfc6455
   [4] http:&#x2F;&#x2F;www.w3.org&#x2F;TR&#x2F;2015&#x2F;WD-webrtc-20150210&#x2F;
   [5] http:&#x2F;&#x2F;www.w3.org&#x2F;TR&#x2F;webdriver&#x2F;
   [6] https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Internet_protocol_suite</code></pre>