Because the article is also full of 238 advertisers.

But claiming the US 5-races system is more significant as a categorization of people than other dimensions for health issues is definitely racist, and is propagating that systemic racism.

Just for another datapoint: two of my great-great-grandfathers in two family branches, in the same small village in France, were respectively farrier and black-smith, while I'm a software engineer. One son of the black-smith continued the trade as a side activity of being a plumber. So I had to think about how my career choice (and those of my siblings, uncles, cousins) relates to theirs.

My own perspective on those trades is that transforming metal was the top engineering scale in the countryside in their era. In those times (XIXth century, early XXth), learning the job required to go work with different masters around France ("tour de France" had another meaning before cycling). While it was still manual work, it was highly skilled job which required both technical skills and creativity, which are also key skills for software engineering.

Note that AI hasn't yet solved making pizzas.

https://go.dev/doc/modules/major-version

Many tools will fail if you break this contract.

https://datatracker.ietf.org/doc/draft-davies-internal-tld/

Deepcopy [1] is a Go package that is still heavily used despite its creator has disappeared 9 years ago. At least GitHub is a stable and trusted host as a distribution point and communication point for users.

[1]: https://pkg.go.dev/github.com/mohae/deepcopy

  > Don’t ask it to show its reasoning in the reply
  >
  > What to do. Remove requests to reproduce its internal reasoning in the reply from your prompts and instructions.
  >
  > Why it matters on Opus 5.5. A request to reproduce its internal reasoning in the reply can be declined. It’s one of the flag categories.
  >
  > How. Ask Claude for what you need instead, for example, “Explain why you chose this approach in three sentences.”

This will happen earlier than AGI.

> So I had a decision to make. I could dive back into PHP after almost a decade away, hand the package to one of the people who’d offered, or let it keep sitting there.

We are in the AI era. As a maintainer of an open source project that I haven't touched for years, I would first start by asking an AI to produce a fix for the issue and check what it proposes. This definitely reduces the mental load and risk of breaking an old codebase that so many users depend on.

Deprecating the project is playing the open source game in an other dimension: tell the word that depending on this project was a bad idea in the first place and that everyone should move on. But releasing a fix on a deprecated project is fine too.

So both actions are on different dimensions, this isn't a choice between 2 options.