Comment by pier25
6 months ago
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.
6 months ago
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.
That's alright now LLM and crypto make this waste seem minuscule
With the TC39 signals proposal, part of that is making progress.
Except React.....
Was react ever about progress?
7 replies →
if (when?) Signals become a standard, React will be in a tight corner if they decide to ignore them
1 reply →
Two way data binding and a jsx clone is kind of all anyone really needs.
React isn’t templating though.
That's kind of like saying React isn't just a bunch of a functions (it is). What do the JSX templates compile down to?
Missed this but - there’s a very meaningful difference between templates and React at least how most people think of templates.
React lets you return dynamic tree structures and insert code anywhere inline in that structure. Most templates explicitly don’t allow that for good reason. Further, most but not all templating frameworks have special syntax for conditional logic and loops.
If JSX is templating then templating has no meaning. Would createElement() be a template? In that case all functional programming is.
Respect for focusing on semantics but not contesting the CPU and bandwidth waste. That takes honesty.
[dead]