ZYbCRq22HbJ2y7

this doesn't even benchmark anything really wrt user experience, so what does that have to do with the article?

the author measured near perfect scores on lighthouse across the board, which, i mean no surprise there?

then it has takes about payloads and ttfb, which is nearly meaningless without implementation details and one being an expert in each framework, imo.

are you just ranting about javascript in browsers because its accepted and articles like this become a place to welcome such without anyone caring about the topic?

> HTML templates (another feature that has existed in most browsers for a decade).

not really? browsers weren't even at the level of baseline a decade ago. microsoft edge on chromium is six years old.

seems like a versioning-induced death

i think a project like this would slough old architecture like mad and let major versions tick, but they forge on...

Depends on the type of water if this a net benefit, but it roughly should be better than the current state of things.

Nothing will bring waters back to their pre-industrial state though.

> speculation needs a cause

it definitely doesn't, as people buy shit all the time on impulse alone. when you have zillions of dollars, that impulse buying can look different, as you kind of say as well.

or... just plain old land speculation?

i read this as: "you are generating code wrong! you need to generate code better, so you don't even need to think about what you are generating!"

seems like a bad UX decision, unless it is somehow summarized at the end or something

it doesn't seem necessary to read a full CoT exchange. rather a final graph of why a decision was made would be ideal for my usage.

you don't worry about it for a couple years and check back to see if its a real problem or a panic induced engagement generator