Apostolos Tsakpinis

@apostolos.tsakpinis.net

CTO, webhotelier | primalres

Been using this repo to iterate on API ideas for a concurrent compatible store for React. Still exploratory but excited that we’re very close to something that we can start trying out with existing data stores and start an iteration cycle based on what we learn.

Mark Erikson@acemarke.dev · 10mo ago

Had a great discussion with @capt.dev about the work he and Justin Walsh are doing prototyping React's "concurrent store" API. Really excited to see the active WIP ideas like this PR: github.com/thejustinwal... hopefully we'll get to try this out with React-Redux soon and see what's feasible!

You can pass sub-classed Promises to React such as in use() with the fields status and value or reason. This allows React synchronously read the value without waiting on a microtask. This is much faster but it also ensures compat when someone needs flushSync(). Microtasks are bad, mkay.

Web development is easy. All you need to do is build a fully asynchronous, distributed system, serving an unknown set of clients over an unreliable network

🎉 After six incredible years at Framer, it’s time for my next step. Today, we’re spinning Framer Motion out as its own independent open-source project, to better serve the whole community. Introducing Motion. For React, and now, for everyone.