Solid video, and it comes from a pretty grounded viewpoint. It’s not very techy or pros/cons-focused; it’s more about the “spirituality” of what we’re even doing with the technology in our lives. They’re obviously not a tech expert, but their mindset and “breaking point” are a lot more relatable for most casual people. This is the sort of realization that people are going to continue having as big tech encroaches further and further on their lives. E.g. their example of “it’s not one big problem, it’s many small problems that add up” with why it’s so frustrating to use Windows, but then why people continue to use it.

It will take a “breaking point” and self-motivated change to critically evaluate the power that you’re giving to corporations and decide that you’re going to accept some discomfort in order to fix it. There will never be a perfect time to effortlessly switch your entire workflow across operating systems. I daresay that if there ever was a point at which switching to Linux was effortless, big tech would flash something new and shiny and make that no longer the case. They prey on keeping people in the path of least resistance, and understanding their strategy is the first step to doing something about it.

Wish people would have realized this a couple decades ago, but it really does feel like Linux is re-entering public discourse as people are getting more and more jaded about their relationship with big tech companies.

Their prices lately have been very unimpressive.

Maybe HDR on linux? I’m fairly clueless about how it all works under the hood, but I’m currently on debian 12 and I’m hoping that by the time 13 comes around it will just work without me needing to do any manual system tweaks. As I understand it, it’s currently semi-working or fully-working in KDE6, but I’m still on KDE5 until debian 13 comes out.

I don’t think ‘cattle not pets’ is all that corporate, especially w/r/t death of the author. For me, it’s more about making sure that failure modes have (rehearsed) plans of action, and being cognizant of any manual/unreplicable “hand-feeding” that you’re doing. Random and unexpected hardware death should be part of your system’s lifecycle, and not something to spend time worrying about. This is also basically how ZFS was designed from a core level, with its immense distrust for hardware allowing you to connect whatever junky parts you want and letting ZFS catch drives that are lying/dying. In the original example, uptime seems to be an emphasized tenet, but I don’t think it’s the most important part.

RE replacements on scheduled time, that might be true for RAIDZ1, but IMO a big selling point of RAIDZ2 is that you’re not in a huge rush to get resilvering done. I keep a cold drive around anyway.

“Cattle not pets” in this instance means you have a specific plan for the random death of a HDD (which RAIDZ2 basically already handles), and because of that you can work your HDDs until they are completely dead. If your NAS is a “pet” then your strategy is more along the lines of taking extra-good care of your system (e.g. rotating HDDs out when you think they’re getting too old, not putting too much stress on them) and praying that nothing unexpected happens. I’d argue it’s not really “okay” to have pets just because you’re in a homelab, as you don’t really have to put too much effort into changing your setup to be more cynical instead of optimistic, and it can even save you money since you don’t need to worry about keeping things fresh and new.

“In the old way of doing things, we treat our servers like pets, for example Bob the mail server. If Bob goes down, it’s all hands on deck. The CEO can’t get his email and it’s the end of the world. In the new way, servers are numbered, like cattle in a herd. For example, www001 to www100. When one server goes down, it’s taken out back, shot, and replaced on the line.”

~from https://cloudscaling.com/blog/cloud-computing/the-history-of-pets-vs-cattle/