For the first time in the 4 years I've been doing Friday streams, I will be having a @react.dev Core Team member as a guest. I'm excited to welcome @ricky.fm on to talk all things React. Past, present, future. www.youtube.com/live/3vw6EAm...

Posted this on twitter as a comparison in the DX of the upcoming SvelteKit (left) and SolidStart (right) Almost everything I care about in DX is identical between these two, but I understand different people care about different things Thoughts? Any meaningful differences I should know?

Lifecycle of a @solidjs.com convert: 1. Why recreate React? Touch grass! 2. How do I use my React library in Solid? 3. Fine-grained reactivity? Sure Jan 4. What do you mean...no re-renders? 🤯 5. Arghhhh React!!! 6. *cornering ppl at parties* Have you heard the good news about signals? 😆

Signals and Sync Engines Name a more iconic duo I’ll wait

i have to admit that i was skeptical about @devagr.bsky.social's talk about fine-grained rendering and sync engines, but he tied everything together really well. if you really care about the fastest possible performance, local-first data and fine-grained rendering are probably the way to go.

My takeaways from this year's @localfirstconf.com Last year we collectively were at the stage of “hey this syncing tech is cool, you don’t need the cloud as much” and “hey, we have a community here, who knew?” This year it felt like the community had more cohesion and sense of identity.

Ooh never thought of it as “progressive JSON” But this is a really cool way to describe the superpower that unlocks so many modern capabilities like RSCs and Single Flight Mutations in Solid Start

Blursed class components in @solidjs.com

Really cool talk on Async and Suspense by @devagr.bsky.social. Love the demo at the end of the talk.

We’re excited to welcome @devagr.bsky.social to Local-First Conf 2025! Dev will show how fine-grained renderers like Svelte and Solid can unlock the full power of sync engines.

I've been making a tetris-like game with a sticky twist for the last year, launched the steam page today along with a little gameplay teaser (🔊 on, excellent music by @keestak.bsky.social) #indiegame Check it out and wishlist now! store.steampowered.com/app/3655080/... Reposts greatly appreciated 💟

just logged into discord and saw an ad the apocalypse is truly here nothing is safe run for your lives

It's so over/we're so back

I just looked at the list of speakers for @stirtrek.com. What an amazing group of people. Almost embarrassed to be included with the likes of @tdesseyn.bsky.social, @csharpfritz.com, @guy.dev, @housecor.com, @devagr.bsky.social, @samidip.bsky.social, and @sethpetryjohnson.bsky.social, among others

holy shit finally we did it people there's official docs on how to build your own framework big props to @mattcarrollcode.com and @ricky.fm for making this happen

It's finally happened! Very thankful to see this huge step forward for the ecosystem! (and yes, I will take a fair amount of credit for pushing to make this happen and providing feedback on fixing CRA for React 19 and the docs updates)

If you can't explain to me when SPAs are the better choice I don't trust your opinion as an engineer

So called experienced engineers who don't realize that architectures are a bunch of tradeoffs and boldly claim that one architecture can "do anything"

Filling out the roadmap for solid-socket and solid-events I have way too many ideas for making these two the absolute best reactivity extensions you have seen

I love @react.dev and @solidjs.com async model so much that I gave a talk explaining why they're awesome But React's "you need a framework to fetch data" has been a little annoying to deal with. Especially because I've seen Solid deliver the promise with only native APIs.

Great talk by @devagr.bsky.social youtu.be/pX5r_jTLbvw?...

A very special @devagr.bsky.social joins me on the first fireside of 2025, and THIS TIME IN HINDI! www.youtube.com/watch?v=rPOT...

We need a name for the blue category

I’m way too excited for the coming updates to @solidjs.com in 2025 - Fine grained async - Mutable derivations - Flush boundaries - Derived signals - Lazy memos - Global batching - Concurrent transitions? Maybe? 🧵

Both RSCs and ZeroSync - promise complete UI-data colocation - achieve low-to-no waterfall navigation - use special compilers and/or semantics - employ aggressive preloading - require stateful servers for UI data

Is this a great use case for react server components? Or is this a great case for preloaded client caches? You decide! Epic Web Battles of Hist.... i mean... Nowadays (explanation in thread)

Let's goooo! I'm super happy for this! @devagr.bsky.social is awesome, and I can't wait to see all the fantastic things he brings to @solidjs.com

🎉Thrilled to announce that I'm joining the @solidjs.com core team! Looking forward to contributing to the future of fine-grained reactivity and helping shape the next generation of web development!

We're thrilled to welcome Dev Agrawal (@devagr.bsky.social) to the SolidJS core team! 🎉 Dev is a remarkably talented full-stack developer passionate about building real-time apps. His skills and expertise will be invaluable as we continue to advance SolidJS. Welcome Dev! 🚀

Glad to see growing interest in @nitro.build ☺️ Thanks to everyone rooted for Nitro @atinux.com @danielroe.dev @evanyou.me @patak.dev @thealexlichter.com @atila.io @brandonroberts.dev @devagr.bsky.social @ryansolid.bsky.social @tannerlinsley.com @thdxr.com many more 💝

Very excited to talk about fullstack reactivity tomorrow on Ryan’s stream!

Friday stream is back with special guest @devagr.bsky.social to talk all about the frontiers of client/server communication and where Signals are going next. www.youtube.com/watch?v=zKXf...

Started making a list of all confs/pods/meetups I've spoken at so far, and holy shit I did not realize the list would get this long

Server Components vs Resumability Discuss

Holy shit what’s happening First Evan, then Dan

CloudFlare Durable Objects with @devagr.bsky.social 😁

FRIENDS STAY WINNING 🥇 Congratulations @devagr.bsky.social & @cmgriffing.bsky.social 💛✨🥳

Well you voted and we have our 2024 winners. Thanks to everyone who participated. I've seen some amazing contributions to the ecosystem over the past few months and so many cool projects I want to try. Big thanks to @sentry.io and @netlify.com for making this possible.

Congratulations to everyone who participated! And special congrats to @devagr.bsky.social and @cmgriffing.bsky.social 🏆 Now that the hack is done, I can finally take all of these amazing projects for a spin and talk about them!!! 🔥

And the #SolidHack2024 winners are... 🏆 🌟 Best SolidStart App: Giffium.com! by @cmgriffing 🎥 🛠️ Best Solid/SolidStart Ecosystem Utility: solid-socket (github.com/devagrawal09...) by @devagr 🔌 Congrats to these amazing projects! 👏

Here's how to better understand RSCs: RSCs are two sets of tradeoff, a technical and an architectural. Yes "tradeoff", not "benefit". It might benefit your use case, but it might also be disadvantage.

She dresses up sometimes

I feel so seen

Happy working on side projects day for all who celebrate! 🥳🤩

Meteor 2014 - signals, sync engine, RPCs, graphql, mongodb, cutting edge tech all around Meteor 2024 - we got promises and expressjs! Meteor evolved backwards

What If: we had socket components? Basically server components, but stateful State could be created on the server, both global and scoped, fine grained renders and events would be delivered over websockets With an easy hatch into client-only state with "use client"

Fellow indians in tech - how would you answer this question? I've seen Indian men represented in the tech community a lot more than other groups like black/latinx/women/non-binary, but not nearly as much as the prevelant demographic, so I could go either way

If you haven’t seen this yet, this is pretty dope.

Look I made the network boundary disappear without Server Components!

Today's conversations showed me that most people (especially in the React community) do not at all realize the power of Server Functions and continue to think that Server Components are the answer to full stack composability