&quot;Just add native support for jQuery and call it a day&quot;
&quot;Just add native support for React and call it a day&quot;<p>We can do lots of amazing things in the ecosystem, but often we&#x27;re working around missing primitives in the platform.  Just &quot;adding native support&quot; for today&#x27;s hottest library doesn&#x27;t fix things properly.  It&#x27;s better to figure out what problem they were solving, and then fix that problem more directly.<p>(jQuery is largely solving &quot;DOM APIs suck&quot;. We&#x27;ve fixed that a little bit, with things like query() (née querySelector(), which was an awkward first attempt at it) and fetch(), but are still struggling to work through browser dev apathy at things like event registration or creating elements.)<p>(Figuring out what problem, precisely, React is solving is exciting and interesting. It&#x27;s non-obvious - it&#x27;s not just &quot;some DOM things are slow&quot;, as there&#x27;s lots of DOM things both fast and slow, and you don&#x27;t need a fancy (read:slow) tree-diffing algo to fix those. There&#x27;s something fundamental going on that we might be able to do better - maybe it&#x27;s more fully separating the &quot;display thread&quot; that contains DOM from the rest of your JS, and letting you do a lot of DOM-ish manipulation in threads other than the display thread. Maybe that means actually using an even more lightweight display abstraction, so you can cheaply spam out updates without having to do expensive diffing first. There&#x27;s a lot of possibilities here.)