soft failures add complexity and ambiguity to your system, as it creates many paths and states you have to consider. It’s generally a good idea to keep the exception handling simple, by failing fast and hard.
here is a nice paper, that highlights some exception handling issues in complex systems
https://www.usenix.org/system/files/conference/osdi14/osdi14-paper-yuan.pdf
it’s safe to assume there are similar issues in closed source. A big part of the snowden leaks was about how NSA could access lots of data at will. It wouldn’t surprise me if they also could execute code.
Also there is stuxnet. But I am not sure, if there were intentional backdoors, or only some “natural occuring” RCE.
“sudo MacOS” sounds like a legit way to describe “gnome+ubuntu”
KDE on steamdeck, because it came preinstalled
Gnome on work-pc, because it came preinstalled
also gnome on notebook, because the multi-workspace thing works very nice OOTB in gnome
Because megacorps are at least “smart enough” to pretend they aren’t trying to take over the world.
there are enough examples for corps doing evil things. You hear about them less often, because they cover their tracks and the outcry is generally smaller than when governments do similar things.
Whereas governments have a tendency to justify a lot of horrible shit for righteous reasons.
corps justify a lot of horribble shit for financial reasons. Is that better?
who else should be a significant backer for an open source project? google? microsoft?
That’s still not how governments work
It would be nice if it worked like that, but we both know it doesn’t
To become chancellor you have to swear an oath on the “schwarze Null”. that you forgot what you did during the largest tax-scam in history
I just want to point out, that what you are saying sounds good in an ideal world. But the realitiy looks different. (I actually typed out some points, but then I remembered that I don’t want to engage in yet another lengthy internet-debate, that ultimately comes down to personal preferences and philosophy)
it’s all of them
for me it was on a pi5. maybe the amd64 was what made it work for me? idk.
snappy it feels versus the official rpi OS
I blame the desktop manager. Once I ditched the default von on the pi, and replaced it with standard gnome, the pi became almost as snappy as my regular notebook.
in general: standard debian should be exactly as light-weight as arch.
how about
X happens
2min later: flashback to X
10min later: another flashback to X
(flashbacks will each time use the same animation, of course)
the linux-file-deletion is used as a example for good software design. It has a very simple interface with little room for error while doing exactly what the caller intended.
In John Ousterhout’s “software design philosophy” a chapter is called “define errors out of existence”. In windows “delete” is defined as “the file is gone from the HDD”. So it must wait for all processes to release that file. In Linux “unlink” is defined as “the file can’t be accessed anymore”. So the file is gone from the filesystem immediately and existing file-handles from other processes will life on.
The trade-off here is: “more errors for the caller of delete” vs “more errors due to filehandles to dead files”. And as it turns out, the former creates issues for both developers and for users, while the later creates virtually no errors in practice.
open suse (or was it mandrake? idk) around 2006. I remember trying it, and thinking “wow. This is trash” and then sticking with windows for 10 more years until giving ubuntu a try (and sticking to it). I tried other non-debian linuxes since then, but they all gave me that “wow, trash”-kind of feeling
you may want to try out kagi.
google get worse, because they have a strong incentive to deliver ads, and a weaker incentive to deliver good results (see Cory Doctorow). Kagi is a subscription service, so their only incentive is to deliver good results.
on HN there are regularly good discussions on the topic, e.g. https://news.ycombinator.com/item?id=37852133
be sure to click on “sounds” an not “open sound settings”, because these are obviously total different things.
Simple
it would be “simple”, if start->settings wouldn’t point me in an completely wrong direction. As it is, you need to know the secret phrase “device manager” (or “control panel” or “management console”) to find the hidden settings-dialogs that will actually solve the problem.
how does it compare to yt-dlp?