HackerX

Account

@Rich_Harris

Ideas
3
Recommendations
9
HN citations
10
Web Development3
View @Rich_Harris on X

@Rich_Harris

Web Development

@Rich_Harris

View on X
Recommended by 3 HN users
From the Hacker News threadUnfortunately, as most of them left Twitter they also temoved all their accounts, so you can only see responses from framework authors like Rich Harris. But here's a very on-brand toot from Alex Russel: toot.cafe/@slightlyoff/1132222807127588… This is the article he's reacting to: dev.to/ryansolid/web-components-are-not…... --- Or here's Lou Verou (a TAG member) calling it hate (this is the mildest reaction, btw): x.com/LeaVerou/status/18401346548522477… and uncritically reposting a bullshit article calling it excellent x.com/LeaVerou/status/18397369083705879… (see reaction by Vue author: x.com/youyuxi/status/1839833110164504691 and x.com/youyuxi/status/1839834941884121363) Note that Lea Verou also says that people decided to fix some things around web components after her post in 2020: lea.verou.me/blog/2024/wcs-vs-framework… Here's Rich Harris (author of Svelte) in 2019: x.com/Rich_Harris/status/11983323985613… Here's the 2022 Web Components Group report: w3c.github.io/webcomponents-cg/2022.html. Notice similarities? Literally everything web framework authors have been saying for ever has been completely ignored in favor if the in-group/tribe. Literally nothing has changed. Nothing at all.@troupoWeb Components: The Framework-Free Renaissance2026
14

@Rich_Harris

Web Development

@Rich_Harris

View on X
Recommended by 3 HN users
From the Hacker News threadI find this tweet about how Google approaches web standards illuminating. To quote: > 1. design a flawed API (it's fine! APIs are hard) > 2. ship it in the most-used browser, despite objections > 3. get cross-browser working group to fix the API > 4. oops, too late, that would break the web twitter.com/Rich_Harris/status/12204127…@throwaway810Google Is Not God of the Web2020
5

More

RSS feed

Keyboard shortcuts