Extended attributes are not KDE specific. KDE just utilize that feature while others just don't

The problem with valve subsidizing it, is that it will make it an attractive choice to those that are not buying it for gaming on steam. After all, it is still just a pc. You can literally do some real work there unlike a console. It may even fall into a company that provides pc leasing service if they are cheaper than some dell or HP or any other mid spec pre-built.

Great write up about the effect of LLM and first point of contact. It still needs to be said however that sometimes the question itself already has an answer and it is buried deep in the other noise. What we can do is make a place that like stackoverflow but without the toxicity

Lemmy sure loves swallowing my reply. To answer your question shortly is an offline first app where the user can add records and the relation during offline and then sync it later after connection is re-established.

To be fair, if the fork sole purpose is to just re-label the software and make people that have irks because of the name start to use the software, who are we to judge?

You mean interaction right? ...right?

You do realize the 13 doesn't have the back part for replaceable dedicated GPU right? That means the chassis itself must be redesigned since the hole will make the previous experience in the 13 different enough.

Our current understanding is not enough to state that with confidence. We used to be so confident with classical mechanics and even claims that physics is almost complete. God knows how long our current probabilistic model will last before we find another better model. It may be probabilistic, or it may not.

To be honest, any hardware company can't really compete with valve toe to toe since valves can cut cost and sell at a loss. But I am interested in how the so-called steam competitor would make the same handheld device. I'm waiting for you Tim Epic.

You are mistaking contributing and distributing.

Edit to clarify: The blog is strictly speaking about the means of distributing the release tarball. Distributing the release tarball has nothing to do with how contribution is accepted or how issue is handled. What they say on the blog is also very clear IMHO and for a good reason. Maintaining infrastructure takes work. Works that if you didn't do it right can be an attack vector. Do you guys remember xz? Do you read how the vulnerabilities came to be? Maintaining a single source of truth for the release tarball can help mitigate that. If one malicious actor can control even one of the distribution channels of the release tarball we get xz 2 electric boogaloo.

Someone is always bound to make this someday. At least the maker is announcing it which is decent enough. Actually, I have always thought that if AI can generate image and voice, what is stopping someone from identity theft? And BAM, we are now in an age where digital data will soon be unreliable unless we have protocol in-place to prove the origin of the data.

What do you mean by C# is "accessable" vs C++? Do you mean it as readability? Or the software availability (compiler, and the tooling behind the language)?