erikpukinskis

It’s funny, Express.js tried this. 4.x was basically a complete piece of software. There weren’t any great reasons to change the API.

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

Any mature SaaS company will have exact measurements of acquisition costs. This is advertising, sales staff, etc.

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

Also worth noting that it’s often not single-node performance that caps throughput… it’s replication.

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.

In addition to Oracle, he owns 1.5% of Tesla and 77% of Skydance/Paramount but those are <10% of the value of his Oracle stake.

Interesting concept. As a side benefit this would allow you to make steady progress fighting SEO slop as well, since there can be no arms race if you are ignoring new content.

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

Does anyone have experience putting their production branches in a separate repo from their development branches?

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 build and my own CDN, it will go down. And I will have to fix it at 2am.

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.

Yes, no recourse. But there are still legal consequences. If Apple blocks certain web content they have a harder time arguing that they are not responsible for blocking other we content: copyrighted material, etc.

They don’t want that cost/responsibility.

What’s partisan about what your OP described? Democrats and republicans alike were entangled in Epstein’s crimes.

What’s the joke?

> Needs reasoning, memory, world models.

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 agree, if there is a death of React it will be killed by Next/Vercel.

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?

I mean, you’re technically correct. But you’re also not understanding the point.

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,

      <b><MyComponent attr=“yes” /></b>

is literally identical to:

      <b>{MyComponent({ attr: “yes” })}</b>

It’s the tiniest bit of syntactic sugar.

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.

“Their” coal emissions

On premise? Or do you build servers in a data center? Or do you lease dedicated servers?