BB_C

If you're not into tiling, install openbox and a panel of your choosing. You will quickly find that you don't need a DE at all.

The maintenance is too high.

acquired knowledge spotted

I will let you on a little secret.

The best "support" you can get is support from upstreams directly (I'm involved in both sides of that equation). But upstreams will often only "support" you when you 1. run the latest stable version 2. the upstream source code wasn't patched willy-nilly by the packager (your distro).

So the best desktop linux experience comes with using rolling distro that gives you such packages, with Arch being the most prominent example.

The acquired knowledge that argues stability and tells you otherwise is a meme.

Because non-open ones are not available, even for a price. Unless you buy something bigger than the "standard" itself of course, like a company that is responsible for it or having access to it.

There is also the process of standardization itself, with committees, working groups, public proposals, ..etc involved.

Anyway, we can't backtrack on calling ISO standards and their likes "open" on the global level, hence my suggestion to use more precise language (“publicly available and sharable”) when talking about truly open standards.

The term open-standard does not cut it. People should start using "publicly available and sharable" instead (maybe there is a better name for it).

ISO standards for example are technically "open". But how relevant is that to a curious individual developer when anything you need to implement would require access to multiple "open" standards, each coming with a (monetary) price, with some extra shenanigans ^[archived]^ on top.

IETF standards however are actually truly open, as in publicly available and sharable.

It implies that the value of their policy work is significantly below...

It's always safe to assume that value to be negative unless proven otherwise actually.

Monthly Reminder: High or low, all Linux usage stats are fake.

@FizzyOrange@programming.dev

BTW, the snippet I pointed to, and the whole match block, is not incoherent. It's useless.

Alright. Explain this snippet and what you think it achieves:

tokio::task::spawn_blocking(move || -> Result { Ok(walkdir) })

Post the original code to !rust@programming.dev and point to where you got stock, because that AI output is nonsensical to the point where I'm not sure what excited you about it. A self-contained example would be ideal, otherwise, include the crates you're using (or the use statements).

Federation is irrelevant. Matrix is federated, yet most communities and users would lose communication if matrix.org got offline.

With, transport-only distributablity, which i think is what radicale offers, availability would depend on the peers. That means probably less availability than a big service host.

Distributed transport and storage would fix this. a la something like Tahoe-LAFS or (old) Freenet/Hyphanet. And no, IPFS is not an option because it's generally a meme, and is pull-based, and have availability/longevity problems with metadata alone. iroh claims to be less of a meme, but I don't know if they fixed any of the big design (or rather lack of design) problems.

At the end of the day, people can live with GitHub/GitLab/... going down for a few minutes every other week, or 1-2 hours every other month, as the benefits outweigh the occasional inconvenience by a big margin.

And git itself is distributed anyway. So it's not like anyone was cut from committing work locally or pushing commits to a mirror.

I guess waiting on CI runs would be the most relevant inconvenience. But that's not a distributable part of any service/implementation that exists, or can exist without being quickly gravely abused.

Definitely don't use axum, which provides a simple interface for routes by using derived traits. Their release cycle is way shorter, which makes them more dangerous, and they're part of the same github user as tokio, which means they're shilling their own product.

this but (semi)-unironucally