Japan is a place of sophistication

It took a bit to get the language server to be able to get the full values

Yeah I can’t do that

I workout consistently. Every time I remember to do planks, I realize how bad I am at it. 5 minutes is a lot.

GitHub - rtorr/nah: NAH is a launch contract system for native applications. It computes how to run an application - binary path, library paths, environment variables - from declarations provided by t... NAH is a launch contract system for native applications. It computes how to run an application - binary path, library paths, environment variables - from declarations provided by the app, the SDK, ...

A very niche, but needed tool I made:

github.com/rtorr/nah

Hey man

Moved away from SSR for now.

Essentially, you can do it for any interaction. Don't need RSC for it, but it definitely _feels_ like updates are smoother. I did move some of the complex client code in the social app, worked really well.

short answer, you were correct and thank you for the context. My react SSR knowledge was still stuck in 2014.

I was able to add the handles to fabric, which worked well. I did find out that RSC was fast enough though. Fetch as soon as possible (even before JS is loaded), stream in data.

Test

A reversible meat tenderizer for $42.95 at Williams Sonoma. It looks like a dildo

looking for a last minute gift at williams sonoma

Shout out to those eating Santa cookies right now

If you can afford it, tip your baristas big today.

Using a prod build/no metro, it is obviously even faster for TTI.

There is before you 🤜⚫🤛 and after you.

SGTM. Appreciate you taking the time. You got me back focused on the thing that could actually be useful.

I just know upstream will do it better, if it is actually planned.

Nodding in agreement

First goal was to fork react and add essentially react-server-dom-native. (done)

Second was getting metro working (done)

Build an app with real data/network (done)

Third was to fork RN to look into what you brought up, which needs to be done.

I got a little distracted :D

It's the same data rendered two different ways.

Definitely more complicate, but TBH, I kind of want to get this idea out of my head I've had for some time. Just holiday fun right now.

Im sure you've gathered what Im trying, but this is to fully render on the server, including layout, and starting the request before JS is loaded.

Essentially, I skip a lot of react on the first pass, but still build out RSC so the react/RN can fully hydrate and take over.

Prerender -> fabric
RSC -> React Reconciler

Rad, I'll take a look.

The video is the feed using RSC to pre render the buffered content, but you could technically do that on the client too, so was trying to think of a "wow" demo.

One thing I have almost working well is bypassing react native for pre rendering to the native layer directly.

the bsky app is already pretty performant. Trying to think of a good demo for RSC on react-native.

@danabra.mov any thoughts?

You would never be able to tell from this screenshot, but this is a bsky client on RNAndroid using RSC.

"I fucking killed it this year"

a long while ago I made the first instagram like app for atproto. This time, its a bulletin board <3

#atproto

Testing my Zig AT Protocol client! 🦎

😓

14? I only have to do 5 and I think that is my limit.