Note that this is a very click-bait-y title: Netflix moved their landing page to server-side rendering only. The main-application still uses React as it was using before.
I don’t think that’s clickbait, if you’re familiar with React you’ll know there is client and server side React. They removed the client-side React.
I tend to disagree: While the “client-side” part surely lowers the expectations on the content, it still claims “Netflix” (all of it!) works without client-side React, which obviously isn’t true. This claim is even more confusing if you ask people to specify what “Netflix” is: Most people would say it’s the player- and browsing-interface.
I’m a still a relative newbie to React, so maybe I’m doing it wrong, but the thing that has surprised when stepping through in the debugger is the number of seemingly redundant calls to a render function. I feel like I often see 2-3 calls when no props seem to have changed, and I assume the redundant result all gets diffed away, but there must be some overhead.
That, and the enormous call stacks. So many function calls to get to my component. Backbone seems much more direct, by comparison.