←back to thread

The time is right for a DOM templating API

(justinfagnani.com)
218 points mdhb | 3 comments | 26 Jun 25 19:23 UTC | HN request time: 0.67s | source
Show context
pier25 ◴[26 Jun 25 22:40 UTC] No.44392178[source]▶
The web really needs native templating, reactivity, and data binding.

I can't even begin to imagine how much CPU and bandwidth is wasted with billions of users downloading, parsing, and executing something like React.

replies(4): >>44392500 #>>44393120 #>>44393371 #>>44400323 #
strix_varius ◴[27 Jun 25 01:50 UTC] No.44393120[source]▶
With the TC39 signals proposal, part of that is making progress.
replies(1): >>44393172 #
CharlieDigital ◴[27 Jun 25 02:08 UTC] No.44393172[source]▶
Except React.....
replies(2): >>44393456 #>>44395794 #
tacticus ◴[27 Jun 25 03:28 UTC] No.44393456[source]▶
Was react ever about progress?
replies(1): >>44394351 #
nine_k ◴[27 Jun 25 06:58 UTC] No.44394351[source]▶
If you valued your sanity when developing complex Web UIs, React was a lifesaver.

DOM sucks though, it's slow, it's heavyweight, it lacks transactions. We're stuck with it, and frameworks like React have to do the DOM diffing + patching thing, explicitly, in JS.

replies(2): >>44394509 #>>44396318 #
1. nchmy ◴[27 Jun 25 12:35 UTC] No.44396318[source]▶
Nah.

https://svelte.dev/blog/virtual-dom-is-pure-overhead

https://news.ycombinator.com/item?id=43971164

replies(1): >>44397821 #
2. nine_k ◴[27 Jun 25 15:59 UTC] No.44397821[source]▶
React appeared in 2013, Svelte, in 2016. Three years is a lot. What comes next can see and avoid some pitfalls of earlier designs.
replies(1): >>44399766 #
3. nchmy ◴[27 Jun 25 19:56 UTC] No.44399766[source]▶
1. I'm referring to the comment that the DOM is slow/bad. It is not. Moreover, VDOM is ON TOP OF the DOM.

2. We're currently living in 2025. React (and SPAs) is not even slightly necessary.