Nick Cherry

@nickcherry

1891 Following

7690 Followers

Nick Cherry pfp

I haven't built any sufficiently complex front-end apps recently, so my usage with Elysia has either by 1) as an API server, 2) SSR (no client-side routing), or 3) API server + a catch-all route to serve an SPA that uses its own routing. But agreed for 3, the DX feels a little funky

1 reply

0 recast

0 reaction

Nick Cherry pfp

Was planning to see if anyone from FC found the app useful, but if so, I would def be interested in doing some kind of integration

1 reply

0 recast

1 reaction

Nick Cherry pfp

I've been using Elysia https://elysiajs.com/

1 reply

0 recast

0 reaction

Nick Cherry pfp

Haha I was kidding, extremely valid question

1 reply

0 recast

1 reaction

Nick Cherry pfp

Apple pushed back a bit on the crypto piece, citing some licenses required for different regions (mostly EU), so I removed everything but US. Hopefully will be expanding to more countries gradually, but need to test out auth (SMS-based) before I try to make that happen. If you happen to have a Canadian (i.e. non-US) number, DC me

0 reply

0 recast

0 reaction

Nick Cherry pfp

"Where does the yield come from?!" For the time being it's just a slush fund of donations :)

1 reply

0 recast

2 reactions

Nick Cherry pfp

In the most literal of ways

1 reply

0 recast

1 reaction

Nick Cherry pfp

Do you happen to have a Chilean (i.e. non +1) phone number?

1 reply

0 recast

1 reaction

Nick Cherry pfp

I’ve been building out a social-ish, AI-moderated productivity app for the past several months. Premise is that users set goals for themselves, post their progress, then get paid for their efforts - up to $400/year in USDC (via Base). Finally got accepted to the US app stores 🚀 https://proof-of-work.app

13 replies

9 recasts

79 reactions

Nick Cherry pfp

UX feels great and the auto-face/text-detection is a nice touch. Well done! 🙌

1 reply

0 recast

1 reaction

Nick Cherry pfp

you are just rawdogging css over here?

2 replies

0 recast

0 reaction

Nick Cherry pfp

yeah i agree that is pretty straightforward. just curious, have you run into any issues wrt caching/invalidation? i don’t have much personal experience there, but have heard some horror stories from others

1 reply

0 recast

1 reaction

Nick Cherry pfp

haha, yeah i believe so. also has a built-in test framework that gets the job done i’ve never migrated an existing node app. i think with this most recent version release, spent a lot of time filling in holes related to node compatibility for that particular use case. the free speed boost is great, but the killer feature for me has always been the first-class typescript support and no need for a compile step

1 reply

0 recast

0 reaction

Nick Cherry pfp

if all the frameworks would just give up on file-based routing in favor of imported functions (which could still be lazy-loaded), i think they could at solve a lot of the issues with minimal impact on any other design decisions.

1 reply

0 recast

0 reaction

Nick Cherry pfp

I haven't spent much time with Remix, but when I've investigated it in the past, I vaguely remembering having a lot of the same issues I do with Next - namely the poor type support and unintuitive/limited middleware. Maybe a skill issue on my part. I do prefer their more explicit route config, though.

1 reply

0 recast

0 reaction

Nick Cherry pfp

Once Bun publishes their Tailwind plugin and adds RSC support, the only reason I think I would even consider Next again would be for the frictionless deployment of toy apps. https://x.com/jarredsumner/status/1883388046814609519

6 replies

5 recasts

40 reactions

Nick Cherry pfp

If you only need compression/resizing, you could look into https://www.npmjs.com/package/react-native-compressor, but for anything more involved I'm still looking for a replacement

0 reply

0 recast

1 reaction

Nick Cherry pfp

That is correct 😅 . I'm not sure what the current state is, but in a simpler time (when there were fewer variables that went into the height of a cast), I think we would attempt to approximate average height based on the data for each cast, then pass the estimated height to FlashList for its internal optimizations. After the cast rendered, we would cache the true height to reference if any of the casts appeared on a different list later in the session. The easier approach is just to ballpark a reasonable average. FlashList won't be perfectly tuned, but will probably be close enough.

0 reply

0 recast

2 reactions

Nick Cherry pfp

also, while it's more of a preference, i prefer that it actually uses pojos, so you get type safety and auto suggest without having to worry about extra compilation steps and ide plugins.

0 reply

0 recast

0 reaction

Nick Cherry pfp

in case it's useful, i tend to use https://tvke.github.io/react-native-tailwindcss/. i haven't done a deep dive, but i assume it's pretty performant given that it's just expose a deep object of view / test styles, doesn't have any runtime compute, and only using a subset of tailwind's classes.

1 reply

0 recast

0 reaction