• 0 Posts
  • 139 Comments
Joined 7 months ago
cake
Cake day: December 22nd, 2023

help-circle








  • i don’t know if i really like that definition. Going by the definition of a laboratory, it doesn’t really make much sense. I mean sure they’re a sterile environment, but it’s incredibly unlikely that a lab is wiped clean and built from scratch, unless you get millions of dollars, and a lot of free time, i guess.

    A lab is merely a place to do work with regard to studying, learning, or improving something.

    People often refer to their “homelab” as an entire server rack, you want me to believe that people are willing to wheel out their entire server rack and discard the entire fucking thing? I doubt it. A homelab is just a collection of gear, (usually commercial networking gear) intended for providing an environment for you to mess around with things and learn about stuff.

    In some capacity a homelab has to be semi permanent, if not for anything other than actually testing reliability and functionality of services and hardware, for the actual services themselves, because a part of the lab, is the service itself.






  • It has to have good wizards that walk you through everything including setting up a domain and email.

    i disagree honestly.

    Part of the point behind self hosting is to empower people with the knowledge and capability that they can do this shit, and fix any problems that result.

    You aren’t really getting people into right to repair, if they aren’t at least espousing it, and trying to engage in it themselves. Sure you can always go to a third party to do something at the end of the day, but with how broad right to repair is, there is almost certainly something in your life that you can fix and repair.

    Like it’d be good that people are doing that, but you also need to remember that this is literally a turn key product, that literally every cloud provider sells, and every company ever who will try to force proprietary buggy garbage on you, will pretend is good, and functional. Will try to sell you, because you don’t know any better. I think it’s just a cultural difference. Car guys that spend time working on their car simply wouldn’t understand the average persons conceptual understanding of repairing vehicles, and vice versa. It’s the same here.

    What you are suggesting here, is a sold, turn key solution, except fully open source, no bugs, no issues, and wide reaching community support. I don’t think that’s reasonably possible.

    I think ultimately, we need to make learning, and accessing learning materials easy (we already do a great job at it) and we just need to get people interested in this shit, some people won’t. That’s fine, they probably know someone that is though. And at the end of the day, that’s probably good enough.



  • genuine advice, i recommend you get into the nitty gritty of linux someday.

    Guis, especially complex guis are just hell on earth. Actually sitting down and learning about what you’re doing, and familiarizing yourself with the underlying tools, is an incredibly good way to get around that problem.

    It’s really hard to fuck up a CLI, and it’s really easy with a certain level of knowledge, to navigate more complex topics and concepts. It’s very worthwhile.



  • Ymmv with Nvidia, but that has nothing to do with development focus and everything to do with Nvidia’s refusal to use the same interfaces Intel and AMD use. Most of the way Nvidia works or doesn’t work with X or Wayland is down to Nvidia’s driver stack. Personally I’ve not had much positive experiences with Nvidia on X.

    that’s what i mean, i don’t blame wayland for it lol. I wouldn’t want to develop for nvidia on wayland either. If nvidia was open and accessible, someone somewhere, would be working on it right now, it’s just how things are.

    That happened literal years ago.

    it’s possible that i missed a few i’ve only been involved for about 4-5 years so far. I don’t know anything about gnome personally because i don’t use it, but it doesn’t surprise me either tbh. I know about KDE because i used it, i know about fedora because i know people who have used it. I feel like i’ve seen more talk about wayland as of recent, but that’s probably irrelevant lol.

    I don’t see the distros that are only switching over now as major contributors to any development specific to Wayland.

    it’s not the distros and their devs, it’s the users and their unique hardware configs. More data makes a more reliable and usable system.

    I don’t take issue with your preferences. Maybe you’re better off with X for now, that’s fine, but you make it sound like Wayland is just full of issues and has barely even entered some kind of pre-release state for software masochists.

    that’s not what i intended, i just said it’s the small issues that appear, and disappear with every few updates, that i don’t want to be dealing with, that’s why i no longer use KDE. I prefer my system to be a relatively consistent level of “broken” most of the time.

    A lot of people don’t have significant issues with that, i believe the previous poster was rather annoyed by them, i imagine they’ll get better soon, but there will likely be hundreds, if not thousands of bugs like this, dependent on specific hardware configurations, that will crop up shortly. And then just randomly disappear, or morph into other bugs, this is the QOL hell part of development.

    X is rather stable on virtue of not being updated anymore, so those aren’t really significant concerns.