Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)LE
Posts
15
Comments
2,750
Joined
2 yr. ago

  • It's impossible to tell how meaningful Backblaze's numbers are because we don't know the global failure rate for each model they test, so we can't calculate the statistical significance. Also there are other factors involved like the age of the drives and the type of workload they were used for.

    buying more reliable devices can definitely save you time and headache in the future by having to deal with failures less frequently.

    That's a recipe for sorrow. Don't waste time on "reliability" research, just plan for failure. All HDDs fail. Assume they will and backup or replicate your data.

  • Any difference you personally experience between the three big brands is meaningless. For any failed HDD you have there's going to be another person who swears by them and has had five of them running for 10 years without a hitch.

    But whatever's cheaper in your area and stop worrying. Your reliability should be assured by backups anyway not by betting on a single drive. Any drive can fail.

  • For home setup you don't care because you should have either redundancy or backup (preferably both).

    So that typically means buying the cheapest HDD that's new and from one of the established brands (Seagate, Western Digital, Toshiba) that's in the correct size for your needs, and you can afford to buy it at least twice (for the aforementioned backups or redundancy), or even thrice, and replace as soon as needed.

    In other words there's no need to speculate on how long an HDD will last, you simply replace it when needed.

    Please also note that HDDs over 10 TB are starting to get increasingly replaced with enterprise models which run hotter and make more noise.

  • Also Android has strategic importance to Google. Their philosophy is to spread out and control their own platforms.

    Normally Google, since they offer a search engine, ad platform and online services, could have stuck to just renting servers and cloud.

    But they didn't, they also created their own massive online storage platform, their own cloud platform, their own browser and browser engine, their own mobile platform, their own PC-based platform, their own wearable platform and so on.

    They will never give up Android, unless perhaps they will have something else already prepared to replace it. But it would be an insane undertaking to move everything over, but to mention having to drag consumers and manufacturers and app creators kicking and screaming every step of the way.

  • DNS at any company tends to be a mess. Multiply that by a thousand for a large multinational corporation. Case in point, here's Microsoft (and these are never going to stop, due to the sheer complexity):

    Even when you use an automated service things can go wrong. For example I use Let's Encrypt but it needs to verify my DNS ownership so I use an API token to let the certbot make the modifications to prove that. At some point I wanted to restrict the token rights so it only has access to certain TXT records (to increase security in case the token every gets compromised). Long story short I forgot to include one wildcard and that particular certificate couldn't get renewed so it was out for the day until I fixed it.

    Manjaro's website is made for presentation purposes and whether it's up or not has no impact on how the distro runs or whether you can download packages. Furthermore it's a completely different team from the distro developers so this has no bearing on the package quality. I've been a Manjaro user when some of the manjaro.org certificates expired but I never knew about it because it didn't affect me in any way.

    manjaro.org uses Let's Encrypt now and it's been recently redesigned.

  • First day at work for junior software engineer, he is super excited and stays late getting familiar with the project.

    Finally he gets up to leave and in the hallway he runs into the CEO himself, looking lost, standing with a piece of paper in his hand in front of a shredder.

    "Oh, thank God," says the CEO, "I thought everybody has left. Look, my secretary has gone and I only have two minutes until I have to be back in the conference call. Do you know how to work this thing?"

    The junior looks at the shredder, notices it's not plugged in, connects it, the thing turns on and he shows the CEO how to put in the paper and press the button. They watch the paper as it starts going in with a sigh of relief.

    "Thank you so much," says the CEO, "you're a life-saver. I only need one copy."

  • Permanently Deleted

    Jump
  • Repology artificially reduces the number of packages instead of reporting the actual number. Which I find highly dubious because most packages have a purpose. In particular for repositories like the AUR artificially eliminating packages goes against everything it stands for. Yes it's supposed to have alternative versions of something, that's the whole point.

    If there wasn't for this the ranking would be very different. Debian for example maintains over 200k packages in unstable.

  • Ironically, if Graphene would succeed, it would lead to a system that's every bit as locked down as a manufacturer's Android. GrapheneOS would also not allow you to have root etc.

    IMO Graphene wants a place at the big player table. They're not in it for user freedoms.

  • Unfortunately that line of thinking stops at the divide between hardware and software. You can legally make a phone manufacturer let you unlock a phone's bootloader so you can install other software, and you can forbid them from denying hardware warranty because you installed other software. Both of which apply in the EU.

    But you can't make them have their software support or play nice with the other software that you install.

    You also can't force manufacturers to open up drivers if they're under NDAs and proprietary licensing (which they often are, due to extensive cross licensing because everybody's owning patents that can lead to everybody suing everybody if they were ever used).

  • Oh and another point: on Debian every package you get is Debian. On Arch the stuff in AUR is not Arch and is not supported by Arch, it's unstable experimental stuff and you take your chances with it.

    In practice, generally, the AUR stuff trends to mostly work fine but it's never guaranteed. It can and it does break spontaneously from time to time.

    This applies to ALL Arch-based distros. So if you plan on counting on AUR to supplement your app needs, please reconsider.

    Debian stable has ~100k stable packages included. Arch has ~15k bleeding edge packages included and ~80k "varies wildly" in the AUR. It will not be the same experience.

    Debian with Steam and other popular desktop apps (like LibreOffice and Firefox) installed from Flatpak will be a much more reliable experience.