• 0 Posts
  • 19 Comments
Joined 3 years ago
cake
Cake day: September 7th, 2023

help-circle

  • I haven’t read through the other responses in the thread, but I don’t think it’s the slightly old software that’s the problem. I think it has more to do with using older kernels, meaning that the latest hardware won’t always be supported (on the stable branch at least - there’s always testing and unstable too of course which may have better hardware support).

    That may have changed with recent releases though - I haven’t used Debian for several years now. But if your hardware is supported then it’s a pretty solid choice.

    Some other people sometimes mention that Debian isn’t as beginner friendly as Ubuntu or Mint, but my experiences have been similar to yours - I found Debian to more user-friendly than Ubuntu for example. Assuming that the hardware works of course - if it doesn’t then it obviously is a worse choice.


  • The whole notion of CSDs is a blueprint example of what happens when UI designers try to think things through too hard. They come up with grand solutions to trivial problems that are so poorly thought through that they create even bigger problems.

    Realistically, nobody is going rewrite their entire application just because of what a tiny cabal of Gnome developers think. Just read this post that was linked elsewhere in this thread. At the end, Tobias is basically arguing that people should go out there and harass the developers of all Linux desktop applications (including the entire KDE project!) to follow through on this ridiculous idea:

    Thus, our goal is for as many apps as possible to have the following properites [sic]

    • No title bar
    • Native-looking close/maximize/minimize icons
    • Respects the setting for showing/hiding minimize and maximize
    • Respects the setting for buttons to be on the left/right side of the window

    Which apps are affected? Basically, all applications not using GTK3 (and a few that do use GTK3). That includes GTK2, Qt, and Electron apps.

    If that alone doesn’t alert people of how out-of-touch the Gnome developers are, then I don’t know what would.


  • The last Windows OS I used was XP, around 2004-ish. Even back then, it was obvious to me that, because it was closed source, that they could one day start acting against my interests, and there was nothing I could do to stop it. I saw open source as an insurance policy - it prevents vendors from acting maliciously against their users. In that very quaint, old time, nobody believed that MS would ever do something like that, but it didn’t matter - the fact was that they could, so inevitably, they would.

    I’m quite proud of how prescient I was when I look at what they’re doing today. No evil is too great to stop a greedy businessman.

    Anyway, I decided to just be brave and create a partition on my main drive and install Ubuntu on it. All I needed to get my work done was OpenOffice, LaTeX, a browser, a compiler, Python… Everything worked better in Linux than Windows so even though I was dual-booting, I practically never used Windows again after a couple weeks. Later on, I switched to Debian, and the next laptop that I bought, I just wiped the hard disk and used Linux for the whole thing. I kept the recovery partition because I was paranoid but obviously never needed it.

    Today, there’s no doubt in my mind that Linux is the best OS. Sure, Macs have better batteries, but if I’m doing productive work, then I don’t really need more than an hour away from my charger. I could maybe agree that the BSDs are better, but I’ve never tried them.


  • It’s a large and very complicated piece of software with a single implementation. It’s practically impossible to fork, so users are forced to adopt whatever changes the maintainers decide to implement. This could include things like forced dependencies (incompatible with mulb libc for example), or other poor design choices (like binary logging, which is very controversial). And it forces its adoption in places that do not want it (as in cases like the one we’re discussing here, where it’s becoming harder and harder for Gnome to be used without it).

    I’m not going to argue about whether systemd is good software or not. But the biggest problem with it is that it’s basically a way for Red Hat to exert control over the entire Linux ecosystem.

    Think of it like Chrome/Chromium. Everybody naïvely thought we were never be where we are today when it was announced, but look at where we are today. While it’s technically open source and an excellent browser, above all, it’s a tool for Google to exert its control over the WWW, such as disabling adblockers, implementing DRM, deciding which CSS/Javascript APIs should (or should not) be adopted, etc. systemd could very well be Red Hat’s vehicle for imposing similar requirements on desktop Linux.





  • This has always been the whole point behind the Trojan Horse that is systemd. Now that Poettering/Red Hat control the entire userspace across virtually all distros, he/they can use it as a vehicle to force all of them to adopt whatever bullshit he thinks of next.

    This is what the Linux ecosystem gave away when they tossed their simple init system to adopt the admittedly convenient solution that is systemd. But in reality, the best solution was always to drop init, and instead replace it with an alternative that was still simple to replace if the need should arise. But now that everyone is stuck on systemd, they’re all at the mercy of Poettering’s Next Stupid Idea.

    Convenience comes at a price. systemd is the Google Chrome of Linux userspace. Get out while you can.



  • It was always obvious to me that as long as I was using closed source software that any day could come when the vendor would screw me over. In fact, it could have been running it with bundles and bundles of spyware already and I had no way of knowing it. So I pledged to start using open source software only, to make sure that wouldn’t happen. First, I migrated all my desktop applications to open source alternatives. Then I finally made the switch.




  • What exactly is it that people obsess over? The desktop environment and terminal customisation? Setting up NetworkManager with nmcli? Using Vim to edit a .conf file?

    Welcome to the crowd! Eventually, you realize that an operating system is just an operating system: something you use to get work done, and the less you notice it, the better it’s doing its job. The pride of setting it all up mostly ends very shortly after you’re done. At that point, you realize that pretty much all distros are the same, give or take.

    That said, there are always moments that make you realize that your OS is amazing. When you’re faced with a new and difficult task that you don’t know how to achieve, then you look at your distro’s documentation and solve it in a few elegant steps. And I’m not an Arch user, but that’s when the Arch wiki will really be your friend, as well as all the other resources that Arch has for its users. I can’t think of examples of these kinds of moments because they’re so rare, but those are the moments that feel great and really make you appreciate your OS.






  • The inevitable fate of any useful software that’s not GPL.

    When will people learn???

    Edit: Ironically, KHTML was originally LGPL. So modifications to KHTML were required to be open source by the license, but Chrome itself isn’t required to be open source (at least as far as I understand it, I am not an expert here). Nevertheless, if it were stronger GPL, then it probably wouldn’t have been impossible to write features like DRM in chrome. So I would have been a bit of an idiot to say that KHTML isn’t GPL (because LGPL is a weaker version of GPL), but in effect, the outcome is the same - all because of that big fat L at the beginning.