I’ve got an approach that I’ve been using where my business logic methods return result types. Then I use helpers in my loaders/actions to handle error results and throw responses with appropriate status codes.

Works but I don’t like how the usage of result types tends to bleed deeper into code

Checking my understanding... with `hyrdate=true`, will the server loader run on the initial document request and make the data available to the client loader immediately without a second round trip to the server after the page loads?

This is great. I've been looking for a clean example of how to accomplish this

convincing devs that SSR was only for seo is one of the worst marketing blunders of the last decade

Fly.io

I used redux-observable for quite a large app a few years back. It solved the problem we had at the time but I would not recommend it. The rxJS api and approach was quite a burden to get my team up to speed with and then became difficult to maintain down the road as knowledge waned.

Ya i see what you mean. I’ve gotten quite used to the remix way recently. Dabbled with Start a bit. Probably need more time with it.

Would you mind giving a high level comparison against remix specifically?

Drizzle or Prisma? Why?