[–] 1 point 3 months ago

“Stable” distros often had a long and risky process of upgrading to the next major release.

But you only do that once every 3-4 years, and you have months to carefully plan ahead.

Meanwhile, pacman -Syu could just provide you a major breaking multi-package upgrade of, say, your desktop environment on any random Tuesday. And then your only options are to either roll the dice and accept that update right then, and deal with all the breaking changes it may introduce, or not receive any updates at all, including security fixes, until you do.

I use Arch myself, and it's been pretty troublefree the past 2 years or so, but it was pretty rough around the Plasma 6 release, and there have been other rough periods as well, like when there were bluetooth/wifi and amdgpu regressions in the kernel.

  • source
  • parent
  • context
  • [–] 6 points 3 months ago

    Just stick these commands in a cron.weekly job or something, so you can forget about it:

    paccache -rk2  # Remove packages from the cache, but keep the latest 2 versions
    paccache -ruk0 # Remove packages from cache that are no longer installed
    
  • source
  • parent
  • context
  • [–] 15 points 3 months ago (7 children)

    I understand the sentiment, but doesn't "the industry" essentially produce things that are for "us", even if indirectly?

    Factories don't exist for their own sake, they exist to make an end product for people. So if you want to change that, we do need to consume less, like the parent you replied to said.

  • source
  • parent
  • context
  • [–] 1 point 3 months ago (1 child)

    I want newer software and I’m just not into going to the work needed to get the things I want running and still being easy to maintain

    I don't really get the "newer software" argument ... they just leapfrog each other every year or so, if you stick to LTS versions. For example, when Trixie came out it was more up-to-date than Noble Numbat (24.04 LTS), and then Resolute Racoon (26.04 LTS) leapfrogged Trixie again, and next year Forky will leapfrog Resolute Racoon.

    Also, with Debian, if the stable release is getting a bit stale, you always have the option to start off with Debian Testing, and get something that's near bleeding edge up-to-date, and then follow testing until the next stable release and then stay on stable.

    Ubuntu Server with CasaOS was fast and easy to setup. Maybe 15 minutes to get he basic file server I want

    Never used CasaOS, but how would the setup process be any different on Debian? From an admin perspective, they're nearly identical ...

    I had a quick glance at the CasaOS getting started page, and not only does Debian have official support but it's recommended over Ubuntu, and the installation instructions appear to be exactly the same.

    To me it just sounds like you're a little bit stuck in your ways.

  • source
  • parent
  • context
  • [–] 1 point 3 months ago (3 children)

    There were still plenty of annoying parts left when I ditched Ubuntu Server as my default server OS for plain Debian. In fact, increasing annoyances was one of the reason I made the switch. This was around 2018 or so, during the 16.04 LTS to 18.04 LTS switch, and I haven't looked back. I'm quite happy with Debian 13 that's currently powering my VMs.

    Fair game not wanting to change a running setup of course, but do yourself a favor and look into Debian the next time you're doing a new install of something.

  • source
  • parent
  • context
  • [–] 2 points 4 months ago

    Sounds honestly like it’d be a bit of a spooky spot secluded in the middle of the night

    Reminds me of a particular scene from the Zodiac movie, which is more or less set in that time period, so yeah spooky indeed.

  • source
  • parent
  • context
  • [–] 3 points 5 months ago*

    Those “personal pet projects” are why Google and FireFox exist as many pieces of their projects often rely on open source components often maintained by a single person.

    Those are a different kind of pet projects, like some small random math library developed by a guy in Nebraska that a big software stack depends on (there's a relevant xkcd about it somewhere). The thing is, if support for such a project stops, the Microsofts, Googles and Firefoxes of the world are able to take over support, pay for it to be supported, or work around it in another way. Plus they are usually careful about which dependency they introduce, if something isn't governed properly or does not have wide community support... it's unlikely to be included.

    Taking on a whole browser as a pet project is something entirely different. Browsers are huge and complex. You're basically betting that mr-cheffy will be able to keep up with all the changes, like security updates, feature updates and bugfixes, that upstream Firefox produces, and that he will be able to keep his own part of the codebase secure, and that he won't get burned out or bored with the project in one or two years.

    For these reasons, I will never put all my eggs into the basket of some 1-man browser project, sorry.

    These pet projects also strip telemetry and respect your privacy.

    Turning off telemetry is just a few clicks, or about:config flags in Firefox anyway. And "respect your privacy" is just meaningless buzzword bingo. If you go to facebook or google in zenbrowser, your data is harvested just like everyone else's. Privacy is a process not a product (browser).

  • source
  • parent
  • context
  • [–] 4 points 5 months ago

    Excellent point. The way a project is governed should always be a consideration when evaluating software, especially for large and complex projects like a web browser that can't easily be forked.

    In the case of chromium, basically all the main developers are Google employees ... so it's no surprise there hasn't been a viable fork.

    I really wish we had something like the "linux kernel" of web browsers...

  • source
  • parent
  • context
  • [–] 4 points 5 months ago (1 child)

    I'd recommend you just switch to Firefox instead, and make that work for you.

    Zen browser (like many of those custom browser forks) is just someone's pet project, and is highly dependent on what Firefox is doing anyway. It's cool to use sometimes, but I wouldn't want to depend on it to stick around or be properly maintained in the long term.

  • source
  • parent
  • context
  • view more: next ›