• 0 Posts
  • 137 Comments
Joined 4 years ago
cake
Cake day: January 26th, 2021

help-circle

  • D_Air1@lemmy.mltoLinux@lemmy.mlFan of Flatpaks ...or Not?
    link
    fedilink
    arrow-up
    6
    arrow-down
    1
    ·
    5 days ago

    I used them for some things, but other things still don’t work quite right. Take Steam for example. I do love flatpaks for testing out apps, things with really finicky dependencies, or pinning a specific version of a software that I want to continue to work in the future. However, for most things, Arch + AUR just covers all my needs without any hiccups.

    To me flatpaks are sort of like NixOS. All the benefits they provide aren’t something I need on a daily basis. Rolling back works just fine 99% of the time with downgrade. I already have system backups. Despite what some articles might insist, things don’t just break all the time. I’m not running untrusted software.

    Basically no solution is perfect, but they don’t need to be. If the benefits I gain can be recreated through other methods without the tradeoffs they introduce, then I will go with that. Of course, that isn’t to say they don’t have their place, but sometimes I feel like some people think that “being designed from the ground up” to handle certain use cases is always better than whatever “cobbled together” thing we currently have and that isn’t always the case. I’m specifically quoting those two phrases because these are the exact phrases you will hear projects using to justify their existence. In fact, I would go so far as to say that some people have outright confused modularity for “cobbled together”.

    One last example I want to make is that I make use of projects like the fish shell and helix editor. In these cases, I find the features they introduce to be worth the tradeoffs and work better because of being designed “from the ground up” to do what they do. However, I don’t make use of immutable systems, containers such as docker, or say filesystems such as btrfs. The features they provide are not useful enough to me compared to the problems they introduce.













  • Is this actually a bug though? I just don’t think krunner or many other calculators for that matter use delimiters anymore. Therefore, the only thing it is changing based on regional settings is the use of the comma or period to denote a decimal.

    I could be wrong considering I had a bit of trouble understanding the post. I just bring this up because in American English there are no delimiters for thousands place or above either.

    Also I don’t see how from this post the decimal point is wrong. Sure it is simplified to one decimal place, but again many calculators do this. Perhaps op simply needs something that provides more fine grained control over number formatting than what krunner is supposed to.







  • Honestly, I would say it isn’t great for anyone who has to do something low level even once. Now that there are open source nvidia kernel drivers that has solved a pretty big issue for most people who would be interested in immutable distros, but there are still many other drivers and issues that your regular user may face.

    One example off the top of my head is that flatpaks specifically can’t ship systemd services if I recall correctly. A lot of wayland apps for thigns like input have to use daemons because of wayland’s security model. Lact for AMD and now Nvidia GPU control, ydotool, or even gui versions of such tools for remapping input.

    Snaps require custom kernel modules that aren’t used outside of ubuntu, so I hesitate to trust them regardless of any of the other issues people have with them.

    This basically leaves appimages which aren’t available for everything and don’t always seem to work at least not as reliably as flatpak. I even tried to package the rstudio forensic software as an appimage myself, so I could have an easy way to use that proprietary piece of software, but I just couldn’t get it to work. I couldn’t get it to work with distrobox either using the official methods they provide to install it on linux. I did get it working in a chroot for some reason, but it had graphical issues. In the end, I made a PKGBUILD for arch and got it working that way.

    The point of all this is that a lot of times people say immutable is great for average, non tech savvy people, but I believe that literally everybody ends up needing to do low level stuff at least once or twice every so often. Which simply isn’t a great experience since you end up having to do layering which throws these theoretical average users right back into the normal complexity of a mutable system, but with even more uncertainty in my opinion.

    Now then with all of these caveats. I do still agree that immutable distros are great for the aforementioned group of people and I know this statement contradicts a lot of what I have described above. The reason why I think they are great for the less tech savvy people however isn’t because of any actual technical merit of the systems design though. Immutable distros are great for people like Linus Sebastion because it limits what they can do. You simply have to accept what is there the same way that you have to on proprietary systems like Mac and Windows. Those systems force you to do things a certain way unlike Linux and that is what people like Linus need because they have no business mucking around with the system to begin with.

    Lastly, all of this only works because devices like the Steam Deck are being run on specific hardware thus guaranteeing there compatibility. This is what we ultimately need. There would be much less need for low level operations to get drivers or change settings to make wifi or audio work right on a billion different devices if these people were buying linux compatible hardware in the first place.