←back to thread

The time is right for a DOM templating API

(justinfagnani.com)
218 points mdhb | 1 comments | 26 Jun 25 19:23 UTC | HN request time: 0.236s | 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 #
agos ◴[27 Jun 25 11:09 UTC] No.44395794[source]▶
if (when?) Signals become a standard, React will be in a tight corner if they decide to ignore them
replies(1): >>44397630 #
1. WorldMaker ◴[27 Jun 25 15:36 UTC] No.44397630[source]▶
Not really? `useSignal` is just another hook React needs as a replacement/augment for `useState` and maybe `useEffect`. Signals aren't that special. Arguably that's part of why a lot of people like Signals as a proposal.

(I'm still of the sort that thinks Signals are just worse Observables, so it's not a proposal I'm particularly thrilled about, but were it to be adopted Signals are easy to use in Observable contexts as well, they are just uglier half-implemented BehaviorSubjects, though maybe with a few extra lint rules to prefer Observable behaviors over Signal ones.)