It's weird, sometimes they are slow for me, too. But everything is done with native CSS transitions. Definitely have to look into that again, thanks for the heads up
> The fact a conscious mind loses capability when brain damage happens shows quite clearly that consciousness as a process is reducible to smaller non-conscious parts though.
I talked to the Cloudflare team at Clerk's ecosystem hackathon last year, showed them Inngest, and they were really enthusiastic about our model. They said something like "we've been thinking about this for some time but couldn't figure it out".
APIs are only part of it. "Flow control" — concurrency, waitForEvent, sleeps, batching, debounce, etc is key. Observability is key. People emulating our APIs is always going to happen, and it's no big deal. The only sad part is that they don't call out any inspiration; we literally asked them to work with us for this with R2 last year.
It's always good to get validation, and I'm glad our API makes sense to folks. The feedback we get from developers is always extremely good.
Well in MacBooks there isn't actually any downward travel, it's just a solid block, there's only haptic feedback to indicate a click has been registered.
I don't see how that's relevant. No matter what the necessary force to actuate the click, it's a larger strain the further off perpendicular your finger is. That means it's different every time depending on where you're clicking.
I just tried several dozen clicks and not one of them moved the cursor at all through the press down/release cycle. Perhaps Apple is running algorithms to correct for this but it is a complete non-issue. You should try it and see how it feels!
reply