• 0 Posts
  • 33 Comments
Joined 9 months ago
cake
Cake day: June 29th, 2024

help-circle
  • 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.





  • 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/



  • TechnicallyColors@lemm.eetoMildly Infuriating@lemmy.world*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    37
    arrow-down
    4
    ·
    2 months ago

    I think it’s hard to dig yourself out of this hole unless you’ve got early retirement on the horizon. The more you work, the less of an outside life you have, and the less you feel compelled to focus on anything but work, rinse and repeat. Your friend probably doesn’t have anything to look forward to IRL, so might as well make more money.



  • Maybe tangential but this reminded me of how much I hate setting up systemd timers/services. I refuse to accept that creating two files in two different directories and searching online for the default timer and service templates is an okay workflow over simply throwing a cron expression next to the command you want to run and being done with it. Is there really no way we can have a crontab-equivalent that virtually converts into a systemd backend when you don’t need the extra power? I feel like an old person that can’t accept change but it’s been a decade and I’m still angry.



  • I’m not sure what a good written guide for manually running linux games is off the top of my head, but generally yeah you install Lutris, install the latest Proton-GE version through e.g. ProtonUp-QT, create a game entry in Lutris with a “Prefix” location dedicated to your wine prefix, pick Proton-GE as the runner, copy the game into the generated prefix, target the normal EXE, and launch it. Sometimes if a game isn’t launching you’ll need to use “winetricks” to install vcrun2022 and dotnet48 dependencies into the wine prefix, since each Wine prefix is sort of like a copy of windows, and windows has a handful of dependencies that games sometimes rely on. I’ve heard you can also just add the game as a “non-steam game” to steam, but I’ve not bothered as Lutris gives more control. Again I can’t vouch for any specific guides, but the keywords from this post should help target a general direction to move in.



  • The previous person was worried that Valve wouldn’t be able to convince “a sizable chunk of users” to move to Linux because all of the software they sell is written for Windows. If we apply a little bit of critical thinking, we realize that Valve has actually already thought of this(!) and applied a different(!) solution that solves the same problem(!) without requiring “everyone to write software for something that’s not the platform nearly all users are running”. If you want to see Valve’s attempt at getting everyone to switch to Linux without using compatibility tools you should look into how successful their Steam Machine campaign was.


  • Nice, I’ll have to watch this. A quick skim through the YT comments says that it’s AMD drivers which is the only thing I could think of. Linux Mint 21 actually has an “EDGE” iso which has a newer kernel version, and Linux Mint 22 is instead going to track the latest HWE kernels, so my understanding is this type of hardware problem should be a thing of the past at least in Linux Mint’s world. I don’t know if Ubuntu has their own plans or not.


  • They’ve more or less already done that with Proton and DXVK. Nearly all Windows games “just work” on Linux without developers needing to change anything. TBH whenever big studios develop Linux versions of games they’re usually not well-done anyway; for now it’s better if people develop with their comfy Windows tools and let compatibility tools take care of the translation. When the balance shifts to Linux dominance we can start pressing on them to learn how to use Linux SDKs.




  • “Escape hatch” specifically refers to the speculation that Valve is positioning themselves in a way that they can’t be forced into paying fees for existing on the Windows platform, and that if push comes to shove they can say they only support Linux now. This hasn’t happened yet, but it’s a strategic stance which will likely prevent it from even beginning to happen. This doesn’t have to do with the Steam Deck specifically; it was also part of their intentions with the Steam Machine and etc.


  • Maybe it needs to be more obvious that there are many ways to do things in Linux, and give new users a short “learning to learn” primer on how things operate differently in Linux-land, and where/how to look online for help. There are always first-boot popups but I imagine most people are conditioned to click out of them without even reading; forcing people to confirm a couple times that they want to skip “very helpful reading” may cut down on people that play the search engine lottery on what information they use for their first steps.

    Also semi-related, I hope that mainstream Linux eventually “un-stupids” computers for regular people again. I get the distinct feeling that Microsoft and Apple have, at least somewhat intentionally, imposed ‘learned helplessness’ onto average computer users. “Oh computers are magic no one knows how they work. We are the only wizards that could possibly understand them and we will sell you the solution.” Windows/OSX/iOS/etc are so locked down that people have rightfully learned over time that if they run into a problem, there really is no solution. I suspect that’s permeating into the new user experience on Linux where people will encounter one problem and throw their hands up and say “fucking computers” instead of using basic problem solving to try another approach.