3 ms·
Highly unpopular opinion: by 2030, React will probably go the way of jQuery (i.e. a highly popular library that was once considered almost an "industry standard
by hliyan 3y ago
Highly unpopular opinion: by 2030, React will probably go the way of jQuery (i.e. a highly popular library that was once considered almost an "industry standard", but later ended up in a graveyard of projects, tutorials and articles).
Difficult to say what the replacement will be, but I suspect it will be some form of plain JS + MVVM architecture, with a VM (view model) with two-way bindings, possibly natively part of the DOM, or even the DOM itself being optimised and async-ed to a point where virtual DOM diffing and similar approaches are obsolete, and an M (model) basically providing a client-side interface for the server API with some level of local caching, and providing an event listener interface for the VM to update itself. You may recognise some of these features from much older libraries, but I think a lot of them will be available natively in browsers (hopefully standardised, or in a darker timeline, fragmented between major browser vendors).
Another possibility is HTMX-like partial updates getting more native browser support, essentially blurring the line between multi-page applications and SPAs.
- threatofrain 3y ago2030 is an extremely long time horizon in tech years, so who knows what will happen by then. By 2030 I think a more interesting possibility is WASM everywhere. Now all language ecosystems ask whether they want to provide some frameworks or DSL for their users to deploy to web.
- satvikpendem 3y agoHere's a good article about WASM based web apps by the author of the HTML5 spec: https://news.ycombinator.com/item?id=34612696 https://news.ycombinator.com/item?id=34612696 Basically he says that we should use WASM for stuff like Figma (which already does use it) or other types of web apps while keeping the DOM for content based websites.
- jimmux 3y agoThat would be great to see. Let the DOM focus on being a good Document Object Model.
- codeptualize 3y agoThe last release of jQuery was last week. It's no longer popular, but still maintained and used. Even if this happens to React, it means it will still be maintained and stable for at least another 15 year. I also think React will evolve and adapt (see RSC which is kinda what you describe). The beauty of React in this aspect is that the scope is quite narrow so it can evolve, as it has done in the past.
- vlovich123 3y agoCOBOL had a release this year. Just because something is maintained for legacy applications, tells us nothing about is health/popularity for greenfield code.