It was a great game!

At this stage, expect limitations, but a question I've asked everyone is: if you choose not to use it yet because its not good enough,I want to know why not.

I would accept a larger fee, too, as well as a higher burden of proof or tracking (e.g. that its going to a company, that it isn't resold, etc.). It sucks AS A USER that we have this chicken/egg problem. As a developer, it sucks for a lot of other reasons.

We had 20,000+ people sign up on day one.

Signup order, no bias.

We invited 5,000 more people to the Rex macOS beta today, about 7,500 so far this week. Last week we only invited ~2500 in TOTAL. We're ramping up quickly. We've now invited ~15% of our total waitlist. We also started the Linux server testing program today with 100 people.

You can't do that when I stop you in person in a hallway, pull you into a meeting room with a whiteboard, and ask you right then and there. The whiteboard defense must happen in person with zero devices present.

We don’t, we invite in order. But only macOS is available for now.

Yep. Clients can of course do whatever they want but the design lends itself to the trie. We compile a set of declarative manifests with golden fixture examples for clients to verify conformance.

Day 1? Like 25,000. Its obviously significantly higher today, that was just first 24h.

No, that's now how this is working. We're inviting with zero bias in the order of newsletter signup. We've done no UA filtering or anything else.

We need forwards compatibility because we expect servers that are wayyyyyy out of date compared to clients.

The latest Rex preview release includes a very important subsystem I've been working on for weeks to enable full forwards+backwards API compatibility with clients and servers. This was gating the Linux test program and massively opening up the Mac test program. We just invited another 1,000 (to Mac) and if it goes well this will step up considerably this week. The Linux test program will likely start this week (separate invite waves amongst existing testers). The API compatibility system is super cool. At a high level: Every API change is a rule on a JSON pointer (RFC 6901). For each message, we compile all the rules between your version and ours into a trie keyed by JSON path tokens. This happens lazily since we don't want a full quadratic explosion (a message with N revisions has N possible chains of length 1 to N). We don't want to build N^2/2 trie nodes when most WON'T be visited. Next, we wrote a custom recursive descent streaming JSON editor (forward-pass only). If a key doesn't match any subtree in the trie, we fast-path copy the full value onto the wire (nothing in it can possibly matter for compatibility). Equal chains of changes are interned to the same pointer, so when we broadcast an event to many old clients, we translate it once per distinct chain, not once per client. The result of all this plus some other work is that we simulated various shapes of 10,000 long revision chains (note: we're on revision 4 at the moment...) with pathological changes of various shapes and an upgrade costs about 35 _microseconds_ on a 20KB JSON body.

Vercel has a slack connect with us. Join that and ask for an invite and you can get one.

Another 1000 invited today btw.

This isn't an AI video. It's real.

Not an AI video, this actually is real lol.

I genuinely hate the marketing trend right now of companies making AI generated videos with their branding/people in it around every single new pop culture or world event. I think its tacky, low effort, and it doesn't look that good at all.

I should add they’ve done this since they were a small startup in case you feel the need to disclaim they can now do it because they’re big (which would be counter to your original claim but alas)