The server-side network model he describes here is the same architecture Meteor is designed with (see this page: <a href="https:&#x2F;&#x2F;www.meteor.com&#x2F;why-meteor&#x2F;features" rel="nofollow">https:&#x2F;&#x2F;www.meteor.com&#x2F;why-meteor&#x2F;features</a>). With Meteor, you get client side prediction and latency compensation (they call it &quot;optimistic UI&quot; now) for free. I&#x27;ve always been impressed they decided to build that, because I sure never would have myself. In fact the Meteor team has always said you need this kind of architecture in order to build true real-time applications. But I haven&#x27;t seen other web-oriented platforms take a similar approach. Did the Meteor team just know something no one else has picked up on (despite it apparently being common practice in the games industry)? What gives?