3 ms·
There’s plenty of real world usecases that demand high interactivity async views. They should be a small subset of the page but there will always be demand for
by dmix 2y ago
There’s plenty of real world usecases that demand high interactivity async views. They should be a small subset of the page but there will always be demand for that sort of real time UX that pure static apps can’t provide. Pretending otherwise at a large company like NYTIMES that has multiple properties with hundreds of millions of visitors is unserious. They aren't running a simple blog or just a newspaper.
I believe React/Vue will ultimately be replaced by recent modern developments using websockets to trigger the delivery of server side static async views. This is how Github/Shopify now does it, ala Elixir's LiveView, and Rails itself also has ActionCable+Turbo/Hotwire. It is far superior as it keeps logic in one place in the backend and in one language. But that is far from mainstream yet like React is and there will always be legacy features that need to be supported.
But hopefully it will become the standard and JS will limited to necessity.
For ex: some components on pages like charts/graphs, multi select boxes with autocomplete, etc will still require JS that websocket/ajax triggered views can't replace. But those are easier to package into standard libraries. Whether reactive vDOM will still be needed for that idk.