> I've often wondered if browsers should ship a standard UI kit with everything taken into consideration (performance, accessibility, etc). They do, it's calle

> I've often wondered if browsers should ship a standard UI kit with everything taken into consideration (performance, accessibility, etc). They do, it's called HTML :) Jokes aside, native HTML obviously isn't enough by itself anymore. But I think that's because it's been neglected, not because things have to be that way. IMO there are two ways it would need to change to compete with these libraries: - A makeover. By 2020 standards, your website is ugly if you don't start from the get-go with a heap of CSS. But it probably doesn't need to be. - Native reactivity. This is something that would benefit everybody. Why in the world do we still need third-party Virtual DOMs implemented in JavaScript when reactivity has so clearly been established as a paradigm? Why don't we have a browser API implemented in C++ for reactive rendering of HTML templates?