• 0 Posts
  • 1.81K Comments
Joined 3 years ago
cake
Cake day: November 14th, 2023

help-circle
  • Yeah, that’s a very common misconception, that you constantly have to “maintain” Arch, as if something happens to it just by having your computer running.

    I do very little “maintenance” other than issue these commands:

    $ paru
    ...
    $ flatpak update
    ...
    

    Before I upgrade the system, I check archlinux.org in order to see if there are any breaking changes that need manual handling. (Has happened maybe 2 times with packages that I have actually had installed, in 10+ years.)

    Then, when paru has invoked pacman and upgraded native packages (from the Arch repo) and starts to upgrade foreign packages (from the AUR), I check the diffs in the package files (paru displays them) to make sure nothing looks fishy. Obviously upgrading Flatpak packages needs no maintenance.

    This all takes about 5 minutes each time I do it, including downloading of new package versions, which is very little time per week. Even less if you do it less frequently, which you definitely can.

    So when you say I do a good job maintaining Arch, is not really me. 😅 The Arch developers have done a superb job for me. And the maintainers of the Arch wiki are also true heroes. I just use it. 👍

    The page you linked to is slightly FUD and yet simultaneously true because theoretically anything can happen and that serves as a disclaimer that the developers shouldn’t be to blame, and nobody is owed support if something were to potentially break.

    Ubuntu broke loads of times for me back in the day. Had to reinstall it several times. And all I did was issue the command for upgrading to a new Ubuntu point release. 😅




  • On Debian, this risk is partly mitigated by the infrequency of updates and by pushing out very well-tested updates to begin with. On Arch, you just have to deal with it every once in a while.

    … not if you just postpone updating to the same schedule as Debian, lol. By spacing your updates out, you reduce the risk of catching breaking changes in just the same manner as Debian. Although Debian probably has more rigorous human testing as part of its release strategy, granted.

    At any rate, I haven’t had Arch break on me due to an update in all of the years I’ve used it. Over a decade by now. And I update very regularly.


  • you’re somewhat expected to at least perform daily updates.

    As an Arch user of a decade by now, I tell you all, you most certainly do not need to update every day, I repeat, you do not need to update every day. That is absolutely not necessary, and will cause much undue stress. I would not recommend that at all. I update maybe once a week. And I find that to be quite consuming as it is.









  • The operand at the top of the stack is used as the second operand for binary operators. Second from the top is used as the first operand.

    Here illustrated using dc, and doing the calculation 3 - 1 and printing the answer with the command p, getting the result of 2. As we can see here with a noncommutative operation (subtraction), in order to illustrate the point, we get 2, rather than -2.

    ~ dc
    3 1 - p
    2
    





  • Great question. Not “hard”, no. 🙂 I’ve been using QWERTY for almost 40 years, so that’s pretty ingrained. Like riding a bike. Also I’m still on QWERTY on my phone.

    But, I do type slower on a regular keyboard nowadays. Partly because I changed my layout, and partly because the ZSA Voyager, which is my main keyboard, is both split and column-staggered, rather than row-staggered like most keyboards. It’s hard to go back to rowstag after getting used to colstag. Rowstag just feels so incredibly wrong. Not at all meant for a human hand. 🤖