• 4 Posts
  • 147 Comments
Joined 1 year ago
cake
Cake day: June 5th, 2023

help-circle

  • I think it comes from diminishing experience windows provides

    An example, since a few windows versions I can’t get to install an old HP printer because they haven’t written the drivers for it. On Linux it works fine.
    You don’t want ads and your os to be sending your passwords who knows where? AFAIK ATM no long time support version of windows provides that.
    My gaming buddy is rather well versed in computer stuff, he’s the person that writes and hosts our discord bots. He can’t make sound drivers to work as he wants. Sometimes things go loud without reason, sometimes mute doesn’t work, sometimes sounds play on an output that according to Windows is muted… Crazy stuff


  • That’s why I wrote it’s another unpopular opinion. Somehow the internet claims Arch is hard when to me it’s been the easiest distro I’ve ever used

    • No GUI bs, unless you install it yourself, that you never know what it does under the hood. The config file you find in man is the config file that governs the thing - easy
    • You deleted a little bit too much? You just reinstall package, like in Slackware - easy
    • You need something from outside the packages? Arch is very well prepared for you building things from source and install it in a sane way, instead of pure make install, like Gentoo - easy
      And PKGBUILD is easy to understand, RPM and DEB package creation is black magic
    • You don’t have a lot of crap in the system that you are not sure you need. Since it comes rather plain, you either install something you want, or it gets installed as dependency

    But, of course, YMMV
    And I’ve tried “easier” distros in the past. Sooner or later it always felt like I need proprietary set of keys to unscrew the lid to flip one small cable


  • I was mocking around with GPU drivers in order to make Podman containers to access the GPU. (…) I don’t have much spare time and I would like to play a game, I used to play before, without spending hours/days fixing issue that didn’t exist last time I played it.

    And

    I had other, non-regular user issues with those

    I think, you should keep these two things (messing with containers accessing GPU and “just play a game”) separate. I mean on separate boxes. Because now you can’t “just play” because you’ve been elbows deep in OS internals. You can’t take apart your fridge and then expect it to just cool the water the next day

    “optimised” for KDE

    Then I’m guessing these might need some KDE envs

    Yes, I use it on a daily basis but there’s no easy way to get it working on iOS/iPadOS.

    Ah, you’re trying to breach the non-open wall. Is there an app on i* that allows you to set up an ftp/http file sharing server on the device? You probably could set it up as rclone upstream


  • started with Mandrake, moved to Mandriva, spent over a year on Ubuntu and recently I’ve been using Fedora

    Another unpopular opinion:
    That’s because you’ve been using distributions that are either behind the times or have a lot of wonky crap added to them that looks like user friendliness when it works and is like fixing windows when it doesn’t (I’ve been through similar path, just with a few other distros along the way)

    Start with Gentoo or Arch (maybe Slackware). These are close to the grass, so the way to set things up is the way to fix things up

    some apps don’t respect desktop scaling

    are these gtk based apps? Different toolsets require different envs

    syncing

    Have you tried syncthing?














  • what happened is the programmer made assumption based on the illusion created by the libraries: writing application on arduino is just like using a library on a unix-box. (which is not correct)

    That is why I have become carefull to promote tools that make things to easy, that are to good at hiding the complexity of things. Unless they are really dummy-proof after years and decades of use, you have to be very carefull not to create assumptions that are simply not true.

    I know where you’re coming from. And I’m not saying you’re wrong. But just a thought: what do you think will prevail? Having many people bash together pieces and call in someone who understands the matter only about things that don’t. Or having more people understand the real depths?
    I’m afraid that in cases where the point is not to become the expert, first one will be chosen as viable tactic

    Long time ago we were putting things together manually crafting assembly code. Now we use high level languages to churn out the code faster and solve un-optimalities throwing more hardware at the problem until optimizations come in in interpreter/compiler. We’re already choosing the first one