I’ve decided to add our SQLite orchestration and replication toolkit to our open-source portfolio, as Leo revealed earlier this week! We’re already running the 'SQLite Engine' in production to globally scale and replicate our SQLite-based data storage at @RONIN. Repo out soon!

I can no longer live without Genmoji — if you aren't already using a bearded camel with the face of the recipient of your message in place of native emojis, I can't help you.

Drastically decreased the install size of Blade by efficiently bundling and tree shaking deps today. A few more tweaks and it'll be deployable to Vercel (Fluid) zero config! Can't wait! Also just noticed we're only 7 stars shy of 100! 🫨 github.com/ronin-co/blade

Thank you so much for 100 stars! 🖤🙏 If you'd like to simplify the data state management in your app, you can already take Blade to prod today! No need for APIs or server functions, just `useMutation` with its advanced query syntax. github.com/ronin-co/blade

Josh tried coding By forcing your app to be rendered client-side, you are neglecting all advantages of RSC. Your initial page load will be a blank screen, your client bundles will become unbearably large (increasing the time to interactive), and so on. Better to stick to the Next.js defaults, IMO.

Watching Anselm Eickhoff demo Jazz - build backendless apps at Local-First Conf. Super exciting!

Blade can now be deployed to @cloudflare and @netlify with zero config, in addition to Vercel and containers! 🎉 Let me know if there are any other providers you'd like to see added. I think Deno and @awsamplify would make sense?

We're working on a docs site for Blade at blade.im — seems like someone already found the link 👀

Thanks, Theo - t3.gg! Working hard not to disappoint you! 🫡

The best loading state is *no* loading state. The best skeleton is *no* skeleton. The best suspense is *no* suspense. Don't make your users wait because of technical constraints. UX comes first. Your users deserve what they want *immediately*, not later.