I wonder if this means I can now also buy a domain via the API?

*update* - seems so, but with some limitations: https://developers.cloudflare.com/registrar/registrar-api/#b...

This bit stands out to me:

> You can’t take five years of community contributions, close the gate, and claim you’re grateful. I don’t think it works that way.

I think it's safe to say that Sam is not impressed with the the Cal.com decision and the way they framed it.

This Show HN post doesn't seem to be by the author and it's not presenting the project in a good way in my opinion. I also don't like the agent framing of the project home page, but after reading the about, I'm willing to tone down my criticism.

The framework seems like an interesting project to keep an eye on.

From the Show HN guide/rules:

> The project must be something you've worked on personally and which you're around to discuss. See these tips about how to present your work.

[1] - https://news.ycombinator.com/item?id=47713650

> Today, with Git, we're all teaching swarms of agents to use a tool built for sending patches over mailing lists. That's far from what is needed today.

ps. I feel like I've been doing python so long that my workflows have routed around a lot of legit problems :)

Almost every time I bump into uv in project work, the touted benefit is that it makes it easier to run projects with different python versions and avoiding clashes of 3rd dependencies - basically pyenv + venv + speed.

That sends a cold shiver down my spine, because it tells me that people are running all these different tools on their host machine with zero sandboxing.

In contrast, typical web frameworks (even static sites) require a code change, build, deploy, etc to update many aspects of a site.

> Undici is an HTTP client library that powers the fetch API in Node.js. It was written from scratch and does not rely on the built-in HTTP client in Node.js. It includes a number of features that make it a good choice for high-performance applications.

[1] - https://nodejs.org/en/learn/getting-started/fetch

  const response = await new Promise( (resolve, reject) => {
    const req = https.request(url, {
    }, res => {
      let body = "";
      res.on("data", data => {
        body += data;
      });
      res.on('end', () => {
        resolve(body);
      });
    });
    req.end();
  });

I assume you have other mitigations in place?