@aboodman @isamlambert I see what you did there 🫣

@aboodman Will that component be under the zero umbrella? Or user land?

@aboodman Yeah that makes sense. How could a story of sharing the sqlite look like? You will have to replicate by tenant and also tunnel queries to the right zero cache instances?

@RyanCarniato Either have variant props or have conditions on the css itself (:has)

I sure know what to do now!

I'm about to talk at a Meetup for the first time! Exciting!

@looxio @zapier Can't blame them

RT @looxio: Thank you @zapier for naming us the #1 social proof solution for 2025 on Shopify!✨

@ryanflorence Very easy to reason about

@jacobmparis In general I hate it. Spacing is a responsibility of the container, not the element. Howeve, you are right. I wish there was a way for containers to declare uneven spacing for their children.

@thdxr Good days are coming! Can't decide what's more exciting. Auth finally being solved, or browsers finally letting us style <select>s.

@thdxr It's either street food or very good restaurants. Everything in between is a waste of your money. Especially when home cooking is fun and tasty.

@frederic_ooo @ryanflorence @DavidKPiano True. But I wonder if it could work for instance methods since there is no 'this'. Only a dangling closure.

@ryanflorence @DavidKPiano And the memory footprint may also suffer when not utilizing the prototype chin

@jamonholmgren Feel the same. I can't have enough of it. After long days of writing code for business, I get home and code for pleasure.

@thdxr We do it in certain situations. Have one route handle the entire workflow. But we do it based on the database state of some entities. I general I like it, it's just a single entrypoint for one state machine.

@devagrawal09 You meant react router v7 right?

I'm gonna take better-auth for a spin. Wish me luck

@thdxr Isn't it a new react meta framework?