3 ms·

Are we not a good way there with the various frameworks that download the application to the clients and read massive JSON objects to dynamically create what th

• jauntywundrkind 3y ago
  The distinction is that these frameworks don't create what the app sees. They create html, that the browser renders. They take data in & transform it into structured hypermedia (html). Because the output is html not structure, users have the agency to run scripts & extensions, doing things like form auto saving or dark mode or modifying the behaviors of sites generally. Part of what's so elegant amazing & compelling about Custom Elements & Web Components is that it helps improve the situation, gets us closer to good with our users. We have lots of promising things we can do to expose the computing on the page, but many popular framework's have steamrolled over a lot of these possibilities to pursue esoteric non-webful industrial fast paths. I'd love it so much if, for example, React Router really rendered & users could live modify the router & that would take effect. But React fundamentally is about using JavaScript state as a model to output html views; it doesnt care about the page. It's a violator of the primacy of the page as declarative source of truth. Ideally all these data objects wouldn't be stored in js stores, but would themselves also be html data islands.