But people hated that. They considered it “unmaintained”. They moved to Koa and Hono because they appeared to be more “actively maintained”.

This is one the the most fundamental components of SaaS accounting, it’s absolutely not a “wild guess”.

Databases are pretty good at quickly adding and removing lots of rows. But even if you can keep up with churning through 1000 rows/second, with batching or whatever, you still need to replicate 1000 rows/second do your failover nodes.

That’s the big win for queues over a relational db here: queues have ways to efficiently replicate without copying the entire work queue across instances.

You could even add options for later cutoffs… for example, you could use today’s AIs to detect yesterday’s AI slop.

GitHub makes it very easy to make a pull request from one repo into another.

This would seem to have a lot of benefits: you can have different branch protection rules in the different repos, different secrets.

Would it be a pain in the ass?

For an open source project you could have an open contribution model, but then only allow core maintainers to have write access in the production repo to trigger a release. Or maybe even make it completely private.

If I use CloudFlare, it will also go down, but probably for less time, and someone else has to be up at 2am fixing it.

> Build what delivers your value.

Like Hershey builds grocery stores?

Like Budweiser builds bars?

This can’t be serious.

We live in a society.

They don’t want that cost/responsibility.

Is that all? So they just need to invent:

1. Thought

2. A mechanism for efficiently encoding and decoding arbitrary percepts

3. A formal model of the world

And then the existing large language models can handle the rest.

Yep, 5 years and a hundred billion dollars or so should do the trick.

I probably shouldn’t care. I’m just not looking forward to the chaos of another full “turn” in JavaScript, akin to query->backbone or backbone->react.

Maybe I shouldn’t fear it. I’ve just yet to see an idea that feels valuable enough to move an entire ecosystem. Svelte, HTMX, etc… where is the “disruptive” idea that could compel everyone to leave React?

What people mean when they say “React is just JavaScript” is…

1) JSX, more than any other templating system, is just HTML interleaved with JavaScript. It’s HTML, and anything between { and } is evaluated as JavaScript.

2) Inserting a React component’s “HTML tag” in your JSX is _actually_ the same as calling the JavaScript function. The HTML attributes are the function arguments. Yes, inside your function there can be state, and there can be contexts, and there are refs. But you get at all of those things by calling JavaScript functions.

Like,

      {MyComponent({ attr: “yes” })}

I feel like too many people think “React is Just JavaScript” is some kind of lie people tell to make React sound cool.

It’s not a lie. There’s a _small_ amount of hand waving around the word “just” but the point is, it’s WAY smaller than what you need to explain the ways Svelte or Vue or Angular diverge from plain JavaScript.

Storage is cheap enough that this attitude is possible.

But I guess keeping all of your designers aware of it across thousands of teams is too hard.

`v-bind:id` and `@click.prevent` are something else. There is nothing like this in JSX. It’s not HTML. It’s not JavaScript. It’s some other language.

If enough people apply some ethical line, it creates a genuine headwind for evildoers.