@slightlyoff I've being doing this for so long (#webdev). I have an inkling that everytime this conversation comes up and the person doing the "front end frameworks are killing us" cautioning - can't or won't actually recommend an alternative - it's because it will never be possible.
Not until the JS baked directly into the browser stops sucking so badly.
It's bandaids on top of wounds on top of bandaids.
@slightlyoff Until we can write *real*, performant frameworks in Native-JS or in Typescript directly in the browser that have better DOM integration.... we will never escape this.
Userland keeps patching the problem with the next bandaid (frameworks, transpilers, livewire, HTMX, etc).... when only the browsers and the creaking, sluggish, joke of JS browser standards can actually fix it.
Browser tech jumped the shark so many years ago I don't know what the damn hold up is.
@slightlyoff They should take the approach #PHP has taken over the last decade - rapid release of modernizing updates, eventually leaving the old behind.
Honestly I'm shocked with browsers being essentially down to a single monopoly now... why JS is still *almost* the same as it was 15 years ago! 🤦♀️
Just fix it #Chromium.... ffs.
@syntaxseed Progress on the web is rate-limited by Apple. If you want that to change (i.e., by Apple facing enough competition that it is forced to staff WebKit above starvation levels), supporting @owa is the most effective thing you can do.
@slightlyoff @syntaxseed I’d also add that it also takes developers to contributing back to standards. It’s not a black box. GitHub was feeding back to Web Standards from the beginning. Exactly what is lacking, and what platform-compatible prototypes are out there—were what browsers asked of my old team the most. GH JS built polyfills, sent patches, demoed how 50 lines of code can be reduced to a one liner if an API was exposed. Things got implemented. The web got better.
