We reworked the Interactions 1. They look *exactly* like Remix Components now, which is what they are, but for events 2. Instead of everything being goofy CustomEvent and event.detail, you can define an interaction of any Event subclass you want, like a TempoEvent! 3. You just

Will package this up and release soon, you'll be able to use it in any framework you like, too! Remix can sneak in anywhere.

(no, I didn't duck punch addEventListener, still kinda want to though)

@ryanflorence Does it include the Dom events / interactions?

@RelevantElement it has, dom.focus, win.scroll etc. but those are just proxies so they don't really cost much you'll import "press" and friends individually as needed so we don't bloat every app with events they don't use

@ryanflorence Congrats to the whole team. That's tiny!

@ryanflorence Dad, I want to be a DJ and play my Remix at Events. > We can't afford all that rig, son, your mum just wanted to redo the kitchen for the 5th time in two years. No, look, it's only 780 bytes, this guy from Florence made it by hand! I saw it on the internet. > Impossible. I

@ryanflorence @remix_run THANK U THANK U for making "Event" a first class citizen. Makes sence because UI frameworks spend 80% of its code defining events, handeling events and firing events. For far too long "The React Brain" had made "State" the focal point of UI framework. Which is weird

@ryanflorence organic-ui is at 292 bytes

@ryanflorence Pfffftt that's smaller than my app not even a real framework smh ngmi

ITS TWO YEARS OLD

Next.js DevRel seeing the jQuery creator hype TanStack

I saw a benchmark today that compared how quickly two schema libraries validate a string is a URI. The first runs 12.0M operations per second and the second runs 8.2M. My question is: in what situation would you need to validate more than 8,200 in a millisecond in one thread?

big git doesn't want you to know this one quick trick