hitekker

I think bcachefs social problems come in part from its hidden technical deficits. “FS implemented as A DB” is a big, leaky idea which undermines userspace claims like “Filesystem code doesn't know about locking or journalling”. Restart-safety being required everywhere is quite a tax.

That leakiness becomes drama when it’s not acknowledged; the energy gets converted to last-minute bugfixes or convoluted workarounds. I’d argue separately that totalization (more than just btrees) threatens a software’s role, and that motivated role confusion forced bcachefs removal from the kernel.

You're flaming someone who expressed the common sentiment: the OP's words makes him seem unpleasant to be around.

If you meant something besides your own moral superiority, say so.

Agreed. Though we still don't have a reason why they rushed a custom preview to a rigorous benchmark competition. Feels like too much hype, and now damage control.

The GP seems to sympathize with the dogpile so they can't (or won't) see what you see.

That's how the mob moves.

> Don’t use async / .await in Chromium.

That's pretty direct. IIRC, the Rust for Linux people also have that refrain informally

I once worked for some professors like that. Nice people who sort-of helped their local community, but were invested in an orthodoxy of causes that proved neither just nor effective

It's odd the commentary assumes that we, the West, are dictating progress on renewables when the world is basically downstream of China's technology and production.

It's like arguing about the scoreboard while someone else owns the stadium. Or pretending to have a seat at a table that's (literally) in another country.

It’s been interesting to watch Artosis (big StarCraft streamer) go silent on Pluto and other bots in the last few weeks. At the start, he was interested and showed a few games where all the pros lost except when they exploited glitches in the AI. Then he lost several times against it and he stopped casting AI games.

Smells like fear

The basic question the plea raises is "how should the long tail of the ecosystem get cut?".

"Upstream has no way to build and test [the long tail] to our own standards" is a certain kind of honesty but not a real answer or a trade-off based in the status quo ante. The status quo, as I glean it, is that C/autotools ecosystem let downstream packagers get from “it compiles” to “it runs” on their own; the new Rust-based one inhibits their freedom to do so.

That said, I respect Astral's decision to prioritize their product by changing their default regardless of the wider ecosystem; I just don't see the point of moralizing it.

This response downplays the portability concern which is the main point of the article. The ask for Gentoo to change its release & update cadence doesn't answer his plea.

As I see it, uv-build is Rust and will stay Rust, so SPARC or address-space-constrained 32-bit targets may never work right. Astral prioritizes its users who run on tier-1 targets, and the cost of their uv-init default lands on the downstream packages that Gentoo has to build. Gentoo wants projects to choose pure python backends to reduce that ecosystem load, Astral would prefer if more projects default to uv-build (IIRC the default went from hatchling to uv-build in mid-2025).

Long-tail & evolution of ecosystem would be a far more interesting discussion, but the broader community has a "we are the future/adapt to us" sentiment that forecloses trade-offs.