> I don't understand why people don't base their apps and frameworks off of standard browser and JS supported techniques like custom elements Because 12 years

> I don't understand why people don't base their apps and frameworks off of standard browser and JS supported techniques like custom elements Because 12 years after their idea was pitched Custom Elements still suck? Just a tiny list of problems with them, with big consequences: https://twitter.com/Rich_Harris/status/1198332398561353728 https://twitter.com/Rich_Harris/status/1198332398561353728 > and template literals with tag functions like Lit The whole field of programming has taught us not to use string-based programming and not to rely on regexps for parsing said string based programming to arrive at results. Also. Why are you against JSX and React, but at the same time happy with such "standard" things from Lit like magical reactive properties and bullshit like ".value=" and "?hidden=" and "@click=" none of which are standard browser techniques. > for choices like JSX that were made in the past when these standards weren't available yet What standards? Very few frameworks want to touch custom components with a ten-foot stick. Yes, most can target them, but very few have the as the underlying abstraction because they are just horrendously bad.