Of what possible purpose is this man's DNA except for framing him for crimes later?

Take a look at Anthropic's repo. They auto-close issues after just a few weeks.

I don't think I've seen an issue of theirs that wasn't auto-closed.

Wait, isn’t software engineering a solved problem?

Yes, that’s why they have such great up time. They don’t go down multiple times per day.

I also hate this pressure of it being on the user to come up with a minimal reproducing example. That means that any bug of any moderate complexity will never get fixed because you can't always reduce them to a few steps and they may be statistical.

A bug is a bug, no matter the developers' opinion or the complexity of the bug.

However there are "bugs" that actually do turn out to be just cosmic rays flipping bits or plain user error. If you as the reporter don't provide enough information for the developer to be sure they are not going on a wild goose chase then it's fair for the developer to not invest too much time.

Sure. But I'm biased because I was a "customer" of a former (large) company's products while also working at that company. So the bugs I would file were the type that a customer would file, but since I was inside, I saw how they were handled. The tactics that my fellow R&D developers would do to claim something wasn't a bug or reproducible were nearly endless.

I think taxes is a way to make someone thoughtful and self-introspective.

They did make the Founding Fathers think quite a lot about some particular thing.

Or if it gets too out of hand turn to the French for inspiration.

I would have never thought it would be possible to wage a war against introspection and make a claim that self-introspection was concocted in the 1820s. It's just patently bizarre.

To claim that Aristotle, Marcus Aurelius, Galileo, Kong Qiu, and the countless other poets, authors, philosophers, and just general people didn't self-introspect until it was artificially introduced in the 1820s is just flat out mental illness.

I have actively told recruiters that tout this guy and his VC firm as a positive that it is indeed not and that I have no interested in working for a place in which he is involved.

It's also bizarre that he's developed a sort of tick that seems like he's breathing in his own smell and breath.

> we’ll explore deeper integrations that allow Codex to interact more directly with the tools developers already use

Gross.

That's all fine. I don't think anyone is upset they got purchased. It's clear it was heading that direction anyway. What everyone is upset about is that they were purchased by OpenAI, who isn't exactly a trustworthy company.

> Just look at what Altman and Brockman tweet about.

Those two are pathological liars, so what they write about means very, very little.

How is uv awesome and Poetry so bad? They do basically the same things except Astral re-invents the wheel but only part way instead of just relying on the existing tools. uv is fast. As far as I can tell, there's hardly any difference in functionality except for it also replacing PyEnv, which I never use anyway.

uv assuming your local Python is busted to hell and back helps a lot with isolation.

Poetry's CLI would often, for me, just fall over and crash. Crashing a lot is not a fundamental problem in the sense you can fix the bugs, but hey I'm not hitting uv crashes.

pipenv was even worse in terms of just hanging during package resolution. Tools that hang are not tools you want in a CI pipeline!

The end result: `uv run` I expect to work. `pipenv` or `poetry` calls I have to assume don't work, have to put retries into CI pipelines and things like that.

Performance aside, uv is more standards compliant than Poetry about the pyproject.toml.

But yes, in terms of user interface they are pretty similar. UV performance really does make the difference.

uv has a lot of sensible defaults that prevent clueless developers to shoot their own feet. Uv sync, for example, would uninstall packages not in pyproject.toml

I mean you don't need to use that then. `uv` is still writing to `.venv` by default and you can activate it with `direnv` or w/e.

the point about defaults though, the default or defacto workflow is uv run

Maybe, but that's not how I've been holding it.

I think I have trauma from virtual environments...

I don't know if it's still true, but ~7 years ago when I last looked at it, Poetry didn't have the kind of UX I have in mind (That Astral/UV do). I remember trying to make it work, and it would choose Python 2 for some reason, despite me never having used it, and it having been obsoleted years before. I remember hitting many problems/errors I can't recall the detail of, but bad UX.

One of them is written in Rust....

What's the poetry equivalent of this?

  uv run --with boto3 python

That command is an environment command. It runs Python in a temporary environment with boto3 installed - I use that trick all the time.

It was very slow compared to uv

Yes, but it still solves dependencies and environments.

"Solves one problem by introducing another, possibly worse problem"

And you wonder why people didn't adopt it.