You&#x27;re missing the point if you&#x27;re holding up HTML&#x2F;CSS&#x2F;JS as a counter-example.<p>In the past, we had a more robust network software ecosystem in which high-level protocol semantics were standardized across vendors, ensuring that:<p>- Multiple server implementations existed, and<p>- Multiple client implementations existed, and<p>- Data (the bits owned by users) were portable across those implementations.<p>This creates a healthy, more resilient ecosystem, within which there does not exist a single point of failure, and competition for clients, servers, and <i>services providing the same</i> is robust.<p>HTML&#x2F;CSS&#x2F;JS do standardize semantics, but they&#x27;re <i>application platform</i> semantics -- we get interoperability and choice across browsers and web servers, but we&#x27;re losing network interoperability between the applications being built on top of them.<p>This isn&#x27;t limited to the web, either: closed protocols and DRM on mobile (e.g. Apple&#x27;s iMessage, Facetime) have produced a similar result. Apple controls the messaging clients, the OS, the network protocol, and the servers. If you want to leave, you lose access to everyone else using the protocol. Resiliency is also lost -- a single party controls the entire infrastructure, including the client software.