Go get 'em, Cory.
-
Go get 'em, Cory.
Web Components Are Not the Future — They’re the Present
An open reply to Ryan Carniato's post entitled 'Web Components Are Not the Future'
(www.abeautifulsite.net)
-
Something unsaid here that I'd add: the idea that componentry should be exciting, or a location for groundbreaking new ideas (rather than just adding all the obvious stuff to web components at pace) is *wild*.
We have real frontend problems that need solving (looking at you, data sync); the internals of the lifecycle for upgrading angle brackets to JS objects aren't one of them. It's time to move on.
-
@slightlyoff while I do not disagree, looking at it from the pov of server side Frameworks, which mostly use html, css and all but barely any client side stuff...
The web components discussion really feel more like the JS components discussion.
Where are we? It feels sometimes like the frontend community decided to leave us on the side of the road.
-
@Di4na It did, and it has not even started to reckon with the real-world consequences. Ryan's platform NIMBYism is just one expression of the deep alienation from user needs I see everywhere in the JS-first discourse.
-
Alex Russellreplied to Alex Russell last edited by [email protected]
We should call Ryan's perspective what it is: platform NIMBYism. Pearl clutching over a non-threat that will, on balance, be good for him too. But he's too invested in the past too see it.
We aren't harming him (or any other framework author) by moving the debate up the stack. We're just declining to subsidise decadence further. Frameworks can create and derive value in the new world too, but holding up progress to make the comparison favourable isn't fair to users *or* developers.
-
@slightlyoff I stopped reading at "Web Components possibly pose the biggest risk to the future of the web that I can see"
-
Alex Russellreplied to Fabrice Desré last edited by [email protected]
@fabrice The post is a real parable about one's reach exceeding one's grasp.
-
Abstraction-itis
Joe Gregorio - REST, Web, Go, APIs, Dad, Husband, Maker, or any linear combination of such. Googler.
(bitworking.org)
-
Stephen John Andersonreplied to Alex Russell last edited by
@slightlyoff I mean… surely he sees the irony in saying - in the same article - “devs need the freedom to try new things” and also “web standards shouldn’t ever evolve to encompass those things”. ️
-
Alex Russellreplied to Stephen John Anderson last edited by
@decoderwheel It's internally consistent; i.e. *"there should totally be more platform features, just not anywhere near me or any of my interests"*.
Will the construction of those features *actually* hurt him or deprive him of opportunity? No. Will it change his *relative* position vis-a-vis developers? Yes.
So now we can see it for what it is: literal platform NIMBYism. Status-anxiety based exclusion.
-
@slightlyoff I'm curious what's your take on https://x.com/BrendanEich/status/1842667582689833457?t=aVRm4m8j8rDMK_RjCxwcKQ&s=19
-
@jlarky What a troll. Things slowed down in WC because Apple noped out and Mozilla failed to implement in a timely way. I covered some of that in this blog-length footnote:
Safari 16.4 Is An Admission - Infrequently Noted
What's going on with WebKit is not 'normal'. At no time since 2007 has the codebase gotten this much love this quickly; but why? Time for a deep dive.
Infrequently Noted (infrequently.org)