But the biggest reason we never did this with jQuery (and it likely holds for React) is that *not enough people use the same version*. There's a constituency that looks like "all jQuery developers", but when you look at it closely, it's a small, narrow per-version constituency.
-
-
JSX is neither HTML nor modern-JS supersetting, meaning you'll need new grammar and parsers. It may not even ben context free. A variant might work, but it *will not* be JSX compatible w/o developers changing their code. ...and if you have to change syntax, why not Lit (e.g.)?
Show this thread -
...and all of that is before we bring in the question of data structures and "diffing". Turns out diffing is slow! Other frameworks are going faster (Svelte, Lit, Vue, etc.) by taking different approaches, but they get similar surface syntax and they are *much* smaller.
Show this thread -
Put yourself in the browser engineer's shoes: you tend a platform that's 20+ years old and which you compete tooth-and-nail on performance about. Someone pitches to you a plan that is slower than other known alternatives and not strict super/sub-setting. Hrm.
Show this thread -
This practice of zooming out ever-so-slightly explains most of the difference in platform vs. app developer behavior in my experience. Platform developers are like Ents; they have responsibility over long time-periods for the things app developers take for granted.
Show this thread -
App developers take it for granted that the language doesn't break whenever new browsers are released, that new features are iterative, that things get faster year-on-year without them needing to re-compile their code.
Show this thread -
Platform developers, meanwhile, have incentive to look at the totality of the web rather than the shouty, shiny bits. You know who's a *much* bigger community than React developers? WordPress-ecosystem web developers. What they need matters more, if we're being fair.
Show this thread -
But we listen regardless, and try to balance needs across these differently-geared timescales and balance them with the relatively limited resources available to each individual browser team. We'll keep doing that, no matter what names
@seldo calls us.Show this thread
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.