[-] UnfortunateShort@lemmy.world 15 points 17 hours ago* (last edited 17 hours ago)

Tons of people making Python comparisons regarding indentation here. I disagree. If you make an indentation error in Python, you will usually notice it right away. On the one hand because the logic is off or you're referencing stuff that's not in scope, on the other because if you are a sane person, you use a formatter and a linter when writing code.

The places you can make these error are also very limited. At most at the very beginning and very end of a block. I can remember a single indentation error I only caught during debugging and that's it. 99% of the time your linter will catch them.

YAML is much worse in that regard, because you are not programming, you are structuring data. There is a high chance nothing will immediately go wrong. Items have default values, high-level languages might hide mistakes, badly trained programmers might be quick to cast stuff and don't question it, and most of the time tools can't help you either, because they cannot know you meant to create a different structure.

That said, while I much prefer TOML for being significantly simpler, I can't say YAML doesn't get the job done. It's also very readable as long as you don't go crazy with nesting. What's annoying about it is the amount of very subtle mistakes it allows you to make. I get super anxious when writing YAML.

[-] UnfortunateShort@lemmy.world 12 points 1 day ago

tldr: Linux can have driver issues and programs or updates might not work as expected. So anything you can expect from any major OS.

Song to that picture (it's fucking awesome btw.): https://www.youtube.com/watch?v=5rjzuejoHKQ

[-] UnfortunateShort@lemmy.world 8 points 2 days ago

(This is also used for Plasma's performance profiles, not just GNOME's)

[-] UnfortunateShort@lemmy.world 5 points 2 days ago* (last edited 2 days ago)

Eh, in terms of UI and shortcuts, Plasma is very close. If you sit a Windows poweruser in front of Plasma, I'm quite confident they will feel right at home.

That's actually how I got introduced to Linux. Then I discovered the Settings app. Fast forward: EndeavourOS btw.

[-] UnfortunateShort@lemmy.world 4 points 2 days ago

In the end, a Heinz a conquered GB. Eat that Brits!

[-] UnfortunateShort@lemmy.world 7 points 2 days ago* (last edited 2 days ago)

Da trifft eher Populismus auf Populismus. Die CDU weiß schon, dass weder Grüne noch SPD viel Bock haben die nächste Regierung mit ihnen zu bilden, aber sie werden alles daran setzen, das eines von beidem passiert. Egal was sie jetzt dazu sagen. Zumindest sofern die FDP nicht genug Stimmen sammelt.

[-] UnfortunateShort@lemmy.world 3 points 1 week ago

Vertrauenswürdige Quellen haben mir zugetragen, dass man mit Excel Tabellen nicht nur Anlagen steuern kann, sondern das auch passiert...

[-] UnfortunateShort@lemmy.world 11 points 1 week ago

Ya know, Signal has been audited multiple times. It's OSS. IT sec elite has looked at it and says it's sound. If anything is plausible, it would be your device spying on you rather than Signal.

What's weird tho is how people think this has anything do with messaging or data privacy. This is about Telegram being used as a public platform. They can't force Durov to decrypt anything, nor do they need to, because they already know your groups...

[-] UnfortunateShort@lemmy.world 4 points 1 week ago

There's a solution for that tho: Tags. If you have sane (default) tags, you type 'terminal' and konsole pops up. And I feel like KDE mostly has that.

[-] UnfortunateShort@lemmy.world 2 points 1 week ago

CC FU-GO-AWAY 1.0

[-] UnfortunateShort@lemmy.world 2 points 1 week ago* (last edited 1 week ago)

You should almost always use amd_pstate=guided/active on anything newer than Zen 2, although Arch Wiki says active is the default since kernel 6.5. Even if it doesn't seem to fix the problem, it's the preferred way to run those CPUs (if it works). guided + conservative scaling governor might help. Maybe it's just a reporting bug tho, wouldn't be a first for AMD.

12

Hey, so I have brand new HDDs I intend to put in a btrfs software RAID. They're Seagate ST4000VX016-3CV104 4TB Skyhawks. Workload is basically write and forget, I will probably never delete a thing.

However I decided to test them first and noticed that after writing about 160 GB, some SMART counters have gone up significantly. Read error rate went from 6.632 to 90.238.872 for example (seemingly all correct by hardware ECC), seek error rate from 143 to 87.661.

Am I reading things correctly? This does not seem like the way healthy drives should behave, does it? It similar on all of them tho. Are they just trash-tier drives they somehow got to work with ECC?

view more: next ›

UnfortunateShort

joined 1 year ago