this post was submitted on 16 Sep 2024
843 points (97.5% liked)

linuxmemes

21180 readers
1239 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

  • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
    843
    Snap out of it (lemmy.zip)
    submitted 1 month ago* (last edited 1 month ago) by 299792458ms@lemmy.zip to c/linuxmemes@lemmy.world
     

    How do you guys get software that is not in your distribution's repositories?

    you are viewing a single comment's thread
    view the rest of the comments
    [–] merthyr1831@lemmy.ml 1 points 1 month ago (2 children)

    Nothing in theory makes that an issue of flatpaks and snap, just that both rely on different means to interact with the host system that have been woefully slow to implement. If enough protocols are developed a flatpak or snap should be as capable as a native app with the safety benefits for free.

    [–] emiellr@lemm.ee 1 points 1 month ago

    While you're right in pointing out that in theory it's basically as capable as native, it's a royal pain in the ass as it is right now, which disqualifies it from a great deal of applications.

    [–] lengau@midwest.social 1 points 1 month ago

    If you look through the desktop portals GitHub, it seems to be a mess of bikeshedding, mostly on the part of a small number of people on the flatpak side. Canonical seem to have been working around this in snaps by writing their own interfaces as stopgaps until the desktop portals catch up, probably because they got such pushback when the similar frustration on the display server side resulted in them releasing mir with its own protocol until the Wayland folks could get their act together.