Austin Malerba's banner
Austin Malerba's profile picture

Austin Malerba

@austin_malerba • 10,448 subscribers

Engineer @ElevenLabs. Prev building https://t.co/znyUVjQF9d. CS degree @RITtigers. All views my own.

Shorts

A grid rotation concept Framer-motion Chakra

A grid rotation concept Framer-motion Chakra

385,999 views

Ringy-dingy thingy

Ringy-dingy thingy

12,725 views

<Nav /> built on Radix by WorkOS nav-menu components

<Nav /> built on Radix by WorkOS nav-menu components

51,331 views

Playing around a bit more with camera utils Added a track(target) function but think i need to implement it better🤔 Framer-motion Chakra

Playing around a bit more with camera utils Added a track(target) function but think i need to implement it better🤔 Framer-motion Chakra

57,999 views

For years i've had this vision for a synchronous reactive ORM with offline support and realtime syncing to other clients. This is the holy grail of state management IMO and i'm finally building it using mobx and yjs. I know that's a mouthful so let me explain: synchronous - there's no promises to deal with and therefore no loading states which leads to much cleaner frontend code. reactive - imagine signals/observables that you can mutate and they will trigger your components to rerender and also will immediately propagate to other users' devices. ORM - what i've made is not an ORM, but it looks and feels like one where you define Models and then you interact with instances of those models. offline/syncing - this is done through yjs, a CRDT implementation, and websockets. CRDTs power many modern collaborative multiplayer tools like figma.

For years i've had this vision for a synchronous reactive ORM with offline support and realtime syncing to other clients. This is the holy grail of state management IMO and i'm finally building it using mobx and yjs. I know that's a mouthful so let me explain: synchronous - there's no promises to deal with and therefore no loading states which leads to much cleaner frontend code. reactive - imagine signals/observables that you can mutate and they will trigger your components to rerender and also will immediately propagate to other users' devices. ORM - what i've made is not an ORM, but it looks and feels like one where you define Models and then you interact with instances of those models. offline/syncing - this is done through yjs, a CRDT implementation, and websockets. CRDTs power many modern collaborative multiplayer tools like figma.

15,170 views

Videos

No more content to load