Reilly

Fun animation ft bun :D

Viewing tech solution as separate entities (infra, db, backend, fe) is a mistake

Good solutions overlap boundaries

Start with UX and work backwards from there

There's a lot of complexity in data fetching in frameworks. What if you could just declare the data you're fetching and the compiler:

- streams it in as props
- implements a component level error boundary
- wraps it in suspense boundary
- fetches in parallel on the server via RSC

Anyone have op?

Setting up SSR (including hydration) with Bun is insanely easy.

Here's a little bonus:

Want your server to reload when you make a change to the code? All you have to do is run:

bun run --watch server.tsx

Bun is the all in one platform designed to build fast apps fast

first merged pr to bun :D

every engineer should read the tigerbeetle's tiger style design doc:
github.com/tigerbeetle/...

v8 isolates are the magic for cloudflare's workers.
At request time:

- typical serverless: boots up full runtime (lambda avg is 200ms) + users code
- cloudflare workers: preboots shared v8 instance so only an isolate (~5ms) + users code is required

read more here: reilly.dev/posts/overvi...

It's absurd how quickly you can iterate on GPU rendered apps with Zed's gpui framework. I'm only a few hours in. It's just so damn intuitive.

The limits are your imagination <3

You can just read source code to understand things

You can just read source code to understand things

Debugged an issue where a shadcn Dialog component was flashing twice before mounting. Memory usage spiking up to 1.4GB. Recorded it in the performance tab and saw that it was the React Developer tools. Removed the extension and the performance issue went away.

2025 will bring a lot more visual based DX tooling - a severely underutilized category of tooling imo

The greatest jr front end eng that I've ever worked with - @kasskodes.bsky.social is looking for a new opportunity. If anyone in the Charlotte area /remote is looking for a kickass front end dev reach out!

Here's a 30 second overview of e2e typesafety in Partykit! Super excited to wrap this up for everyone to enjoy! <3

update on upgrading type safety with
Partykit (s/o to @threepointone.bsky.social)

you now get inferred types on not only your type of message but bc of discriminated unions.
The dx is 10x better with these new types!
Next step is transferring this data to the client.

Default to variables for everything. Use state when you HAVE to.

Targets esm by reillyjodonnell · Pull Request #249 · robtaussig/react-use-websocket The js ecosystem has shifted to supporting esm by default. These are the small changes we need to make that transition! If instead we are wanting to target both cjs and esm happy to make a pr for t...

My first pr to an open source lib just got merged! github.com/robtaussig/r...

I followed you back 🫡

mylo xyloto is one of my fav albums of all time

Yes for sure! You start by making a schema like this:

Then you'd pass it to your class that implements Party.Server.

step 1 done

partykit inherits a problem of crossing network bounds—no e2e type safety. But imagine you run a command that requests types from your PartyKit server, which introspects and responds with a type snapshot. Add a wrapper & voila e2e type safety with PartyKit. POC soon!

Happy birthday!!

Biggest advice for new developers is don't blindly do tickets & do stuff bc it says to do stuff. Instead think through what the ask really is. Make sure your ticket actually leads to the desired outcome.

I've been spending more time contributing to open source lately in projects like Bun and react-use-websocket. Got to explore a lot of the codebase from the CLAP zig code, to initializing the VM & handing off execution to JavaScriptCore, the engine that runs the JS