Rocicorp

Sync engines.

Rocicorp's year in music 1. How It's Done - Huntrix x.com/aboodman/statu…

@LaneBrain_ It was made before the transition. But we miss the little blue bird, too.

i have so much respect for @rocicorp's website twitter icon: long live the little blue bird... 😍

How does @rocicorp keep Zero fast? 🐰 Bencher: bencher.dev/perf/zero

The most annoying problem for Zero's launch was what bug tracker to use. GitHub is way too slow, and Linear doesn't have public bugs or permissions – both required for OSS projects. This was driving me nuts, until I realized the only possible solution… ⏩ (link in reply)

Dev is hired

General purpose sync for the whole web.

@geclos @victorianoi @replicache > zero sync caches on We see what you did there.

@victorianoi Presently for a SPA I'd still go with a dedicated BE and FE. In the future I hope local-first with @replicache or zero sync caches on.

After 2 months with @nextjs : 1/ Server actions are a fantastic abstraction 2/ RSC is complex and not ideal for SPAs— will likely remain niche (SEO focused, static pages, etc). 3/ file-based router is meh 4/ API endpoints are an afterthought

@sumek Sorry, no.

Beyond excited to share that Matt Wonlaw (aka @tantaman) has joined @rocicorp as our seventh partner. Matt is well-known in the local-first community for his work on vlcn.io and related projects, and I'm delighted he has chosen to join forces with us. We've all been working together now for several months, and I cannot wait to share the results. Let's just say that they will be _materializing_ very soon.

When processes evolve separately from each other, their state diverges. That's why we're kicking off a newsletter. Issue 001 of "The Sync" covers the last six months of changes to @replicache and @hello_reflect. Check it out at rocicorp.dev/blog/the-sync-….

We've added a new partner to @rocicorp! I've known Darick Tong for about fifteen years – he was one of the principal engineers behind the Gmail backend, and widely respected at Google. More importantly he's the person behind the 💩 emoji. fastcompany.com/3037803/the-or…

I am extremely delighted to share that @alexkingsays is joining @rocicorp to lead design. My entire career, I have loved collaborating with great designers. There is just something about a tight feedback loop between ux creativity and engineering creativity that often makes magic happen. Alex has been heroically helping us in nights, weekends, and other miscellaneous scraps of time for the last year. And even with only a tiny fraction of his attention, the results have been *amazing*. Collaborating on replicache.dev has been some of the most fun I've had in years. I could not imagine a better design partner for our company, and cannot wait to share what we have in store next.

@maccaw @rocicorp But I guess with the caveat that this is still a work in progress, here's the comp explainer we share with candidates at Rocicorp that explains how our company works: replicache.notion.site/Rocicorp-Compe…

Today, @replicache is entering General Availability! This means Replicache is now ready for use in production, and caps two years of iteration with customers like @vercel, @monday, @placemark, and @assetbots. For more, check the new Replicache website: replicache.dev

A few small open source JS utilities we recently factored out of @replicache thanks to @ErikArvidsson and @equanimityhow: github.com/rocicorp/lock github.com/rocicorp/resol… github.com/rocicorp/logger A few words about each below...

@DStonee1 Thanks for the interest @DStonee1 - eventually, but not right now. Sorry! :-/.

Here's something fun for a quiet Saturday night: 👊🏽 github.com/rocicorp/fract… 🤙🏾 github.com/rocicorp/fracd… Standalone JS and Go impls of Fractional Indexing, as recently popularized by @figmadesign and described at @dgreensp/implementing-fractional-indexing" target="_blank" rel="nofollow noopener">observablehq.com/@dgreensp/impl….

Hello, world. roci.dev