Good solutions overlap boundaries
Start with UX and work backwards from there
Good solutions overlap boundaries
Start with UX and work backwards from there
- 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?
- 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?
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
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
github.com/tigerbeetle/...
github.com/tigerbeetle/...
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...
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...
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.
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.