I don’t think RSC itself being a React feature is a problem - it unlocks some interesting patterns.
The issue is the tradeoffs involved in making it work. It leaks into, or even demands control over layers that are previously not in scope for client-side frameworks. This creates heavy complexity (and associated mental overhead) in order to get the main benefits it promises.
React team made a bet that they can work with Next team to polish the DX to the extent that the benefit would essentially be free - so that RSC can be a silver bullet for all kinds of apps, and that it would become the idiomatic way to use React. IMO, that bet has failed.
Hi, Trailblazers!
Robin is greeting! 👋
A thrilling collaboration TWS between @honkaistarrail and @MoondropLab! Get ready to immerse yourself in dynamic melodies with Robin! 🥳
🎉Follow+Like+RT, we're giving away Star Rail ROBIN's CD to 5winners! Ends on Oct 18 (3PM UTC+8)! #Giveaway
A newly developed wireless earphone.
Coming soon!
#StarRail #MOONDROP #水月雨 #崩壊スターレイル
I've been looking at a lot of comments (including those on reddit) around this, and I'm still seeing many of the exact same arguments from 4 years ago when Composition API was first proposed.
I've actually written a lot about "Why Composition API" in the docs, not sure if they ever bothered to read it: https://t.co/oPfPPEqpSV
I think it's fine if you still prefer Options API after reading it - after all you should go with what makes you more productive. But (1) it should be an informed decision, and (2) maybe the problems Composition API solves do not apply to you, but they do apply to many other Vue users.
Granularity has different levels. React with the compiler is now fine-grained at the component tree level, but inside it’s still coarse (vdom).
Solid is what I’d call truly fine-grained as the granularity can be all the way down to binding level. Vue 3 is close by leveraging the template compiler, where Vapor mode (our WIP new compilation strategy) will have the same level of granularity as Solid.
Devin is not really beyond what I imagined it would be like - and to be honest, quite underwhelming. A developer that gets things done only 13% of the time is a liability not an asset.
Rolldown is currently 1.4~2x faster than esbuild when bundling pure esm modules.
We don't show benchmark graphs yet because Rolldown is not yet feature complete, but we have a decent amount of performance budget for the advanced features.
Just one more state variable bro. Just one more hook and the page will have everything it needs. Just one more state variable please bro. Bro? Add one more state variable please bro
SolanaFM’s mission remains unchanged — bridging the gaps of data accessibility on Solana.
Over the past few months, we’ve cooked up the most extensive indexing platform to help you handle all things data.
Introducing the SolanaFM Developer Portal.
https://t.co/bot7ddLhVU
i mean it sucks I tweet so little here, but sometimes i wonder how a company can build and ship if they tweet so much just to generate clout and end up not doing work much quicker than they did.