He/Him Content Creator Engineer, @codemod Core team, @solid_js Core team, @ripple_ts https://xitter.cf/t.co/bqdpqbi9T3 https://xitter.cf/t.co/TyM2hVeVuJ
Wichita, KS
Joined December 2012
- Tweets20.2K
- Following1.6K
- Followers15.8K
- Likes67.3K
Pinned Tweet
Everyone wants to do Code Mode agents
No one is truly embracing Code Mode
So I made a new agent with Code Mode as the foundation
Meet OC++ (a fork of @opencode)
youtu.be/RTJZRF2sotg?si=r9fC…
you want liveview in js, but actually good? we got it!
The stream is back tomorrow. I'm going to talk about my exploration into the last quadrant of my unified architecture grid: Live Server Components.
youtube.com/live/Sr1z-u3UxTA…
Dev Agrawal retweeted
The stream is back tomorrow. I'm going to talk about my exploration into the last quadrant of my unified architecture grid: Live Server Components.
youtube.com/live/Sr1z-u3UxTA…
live now! hop in and learn why @solid_js is the framework your agents should be using
Reminder if you want to learn about solidjs. Ill be speaking here on Oct 22nd
luma.com/techtank-framework-…
Dev Agrawal retweeted
Reminder if you want to learn about solidjs. Ill be speaking here on Oct 22nd
luma.com/techtank-framework-…
powersync continues to be the most sensible sync solution and it's not close
let’s talk about sync
ever since watching theo’s videos about t3 chat local sync, I wanted it for smry.ai
but as I worked on it, I realized it’s not a good-to-have, it’s a must-have for a reading assistant, as your reading history needs to load instantly.
also users want to own their data, which they do if it’s cached on their own browser
i evaluated every provider: zero/electric/etc, even built my own shitty one!
but nothing was as good as powersync, which is super cheap, scales like crazy, has a drizzle integration, and has a team with actual support (also everyone else in the space seems to die/get bought)
powersync was the best solution for sync, but really the team was the best part
i’m able to work much faster now that I’m not worried about hand-rolled sync breaking with every change, and with all code written by agents it’s good to have a tool that has the things they need to succeed
Dev Agrawal retweeted
I always come back to this writeup from @Rich_Harris. It's been the oracle of most JS framework compiler work the past decade. This is why others failed where Svelte succeeded.
AI suggests we rethink this. We want restriction, not extension.
gist.github.com/Rich-Harris/…
update: more than 20 issues were found through this migration and fixed.
@openclaw was able to migrate to Solid within 2 weeks. now it can be done even faster!
what are you waiting for? don't you want a faster and better experience for your users?
Dev Agrawal retweeted
I am here once again to say “put up or shut up”
One million to open source this year, as we continue to give back to the ecosystem via the pledge.
More than half has gone directly to your favorite open source developers.
blog.sentry.io/another-year-…
best part about migrations like this, they help us catch and fix a bunch of issues
pointed opus to openclaw's solid migration PRs and it already found atleast 7 issues that can be fixed in the framework and documentation to make this sort of work even smoother.
Two weeks ago I kicked off a loop to move OpenClaw's Lit-based Web frontend to Solid 2.0.
Took ~6 days until we could remove Lit, and another week to move patterns to idiomatic Solid.
I checked in with the session every other day, overall the process was mostly automatic. Took about ~600 PRs.
Result: Smaller JS and CSS footprint and much more fine-grained update control. Everything feeling more snappy and responsive. team.openclaw.ai/chat/robocl…
“Would I still choose Solid for this UI?
Yes—because of architectural fit and predictable update scope.”
I love this new world where you don’t need to know why Solid is better for your app, your agents already know and can help you make that choice
Two weeks ago I kicked off a loop to move OpenClaw's Lit-based Web frontend to Solid 2.0.
Took ~6 days until we could remove Lit, and another week to move patterns to idiomatic Solid.
I checked in with the session every other day, overall the process was mostly automatic. Took about ~600 PRs.
Result: Smaller JS and CSS footprint and much more fine-grained update control. Everything feeling more snappy and responsive. team.openclaw.ai/chat/robocl…
Turns out good abstractions are beneficial for agents
You are doing your agents a disservice by not giving them the best tools available today
Two weeks ago I kicked off a loop to move OpenClaw's Lit-based Web frontend to Solid 2.0.
Took ~6 days until we could remove Lit, and another week to move patterns to idiomatic Solid.
I checked in with the session every other day, overall the process was mostly automatic. Took about ~600 PRs.
Result: Smaller JS and CSS footprint and much more fine-grained update control. Everything feeling more snappy and responsive. team.openclaw.ai/chat/robocl…
Dev Agrawal retweeted
Two weeks ago I kicked off a loop to move OpenClaw's Lit-based Web frontend to Solid 2.0.
Took ~6 days until we could remove Lit, and another week to move patterns to idiomatic Solid.
I checked in with the session every other day, overall the process was mostly automatic. Took about ~600 PRs.
Result: Smaller JS and CSS footprint and much more fine-grained update control. Everything feeling more snappy and responsive. team.openclaw.ai/chat/robocl…