yes, it’s a rant. I don’t care.

Back in the days drag and drop was working perfectly fine, but now it’s a pain to use. I just installed mkvtoolnix dropped two files into it and it worked. Wanted to add another one and it didn’t. Guess it’s because it’s in a network share and for some reason that matters. Adding the file via the menu works though wtf? Reinstalled mkvtoolnix. Now natively instead of flatpack and now dropping from the network share works, too. Guess it’s some sandbox permission thing and who doesn’t love fiddling with permissions on a weekend.

Btw dropping a file into the file open dialog window also does not work when the program is installed as flatpack. Try explaining that to your mom and then think about why most people think linux is to complicated.

Also remember how you could drop a file instead of pasting its path? I just tried that to add the path of a video into a text file and it inserted the video into the text. Of course it froze the text editor. Great.

Also way too many times firefox opens a file then I drop it in instead of uploading it to the cloud storage I have opened and unzipping files by dragging them out of the archive manager is not possible for the last couple of years.

Honestly I don’t care about workarounds or if it’s a wayland, grnome or flatpack problem. These are basic functionality that I expect to just work

    • marius@feddit.orgOP
      0·
      4 months ago

      True, but for some reason in the software center flatpack often is the only option even when it’s also in the repository. Sure I could install that one using the command line but then we are back at workarounds. On the other hand, not using flatpacks is also just a workaround

      • kumi@feddit.onlineEnglish
        1·
        4 months ago

        It’s not as black and white as they say. Flatpak is not a bad choice per se but not without tradeoffs and they can come with catches like this because of the security model. There is no one-size-fits-everyone here. If you want all your apps to have access to everything your user does and value convenience over the sandboxing, flatpaks might not be the best choice for your situation. Also like for any repo with external third-party uploads, quality varies a lot between apps and maintainers on flathub. Some are excellent and some are in a sorry state. Before installing from fllathub its a good idea to some basic due diligence on the package and maintainer before jumping in.

        I agree with the IanTwenty that the UX has room for improvement in making it more obvious what’s going on and making it easier to manage customizations and overrides. For the time being, getting comfortable with Flatseal and learning more about Flatpaks seems like the best way for a user to make it work for them if defaults don’t work out.

        Flatpak has tradeoffs and whatever is on flathub is not guaranteed to always be your best pick. That doesn’t make it Bad. Going as far as calling them harmful in general is hyperbole. It can still be a great option for many users.

  • just_another_person@lemmy.world
    1·
    4 months ago

    Comes here to rant about something…

    Doesn’t even understand what he’s ranting about 🤣

    Wanna give some details here, chief? Maybe someone can actually let you know what’s going on or fix it. What DE are you on, first of all?

  • Eggymatrix@sh.itjust.works
    0·
    4 months ago

    I said it and I’ll say it again.

    Flatpack solves the wrong problem for the wrong people, stop recommending it, kill it with fire and spread the word.

    • nocteb@feddit.org
      1·
      4 months ago

      I think it’s a good idea for closed source stuff, but the disadvantages of it are greater than its usefulness when an app can be easily compiled for the distro.

  • doodoo_wizard@lemmy.ml
    01·
    4 months ago

    Yeah it’s always sucked and tbh the only place drag and drop has ever worked close to predictably is on the mac.

    As someone who uses linux, mac and windows, if you rely on drag and drop working right you’re probably best served by using macos. Windows is a distant second but if you get familiar with its eccentricities then it’s doable too.

      • doodoo_wizard@lemmy.ml
        0·
        4 months ago

        Op one of the reasons it’s frustrating for me to see so much focus put on flat packs, snaps, docker images and the like is that they manage to excel at doing their one expected thing, but throw everything else out by the wayside.

        Frankly I think their prominence is a direct result of the way their goal is structured: make sure the “🚀getting started” section of the git/wiki works 100% of the time.

        It’s a distillation of the poison ethos of technology companies dripping into the open source world. We are now moving fast and breaking things. Oh, the things we broke are the users environment? Well, it just so happens that we sell a premium product that integrates properly for a small subscription fee.

        • MotoAsh@piefed.socialEnglish
          0·
          4 months ago

          OFC somene who favors macos doesn’t understand dependency hell or general IT frustrations…

          There’s a reason containers and immutable/atomic linux flavors have become popular… In fact, several. Good ones.

          • doodoo_wizard@lemmy.ml
            0·
            4 months ago

            Static linked libraries shipped with software exchange dependency hell for environment inconsistency.

            Extensive handlers and api calls can work around that, but then you start building the windows nt system all over again.

            The reason atomic/immutable became popular is because two generations looked out upon the plains and wept because there were no more useful programming problems to solve but had to suck it up and manufacture some so they could solve them to pad their resumes in order to get faang internships.

            • MotoAsh@piefed.socialEnglish
              0·
              4 months ago

              Yep, just full-throatedly out here yelling how you don’t understand the problems being addresed…

              • doodoo_wizard@lemmy.ml
                0·
                4 months ago

                I’m gonna go out on a very stable limb here and recognize that containers, immutability and atomic(ism?) are solutions to wildly different problems and the set of circumstances that allowed them to be viewed as acceptable approaches stem from the costs and reliability of storage and bandwidth and not from some form of correctness.

                Now that at the very least storage and the memory required to page it are getting expensive, you can expect people to become more vocal about how badly implemented these solutions are, weather or not they’re able to actually articulate it in the face of you stamping your feet and saying “nuh-uh”, as I have, or not.

                I can tee you up, holy warrior of containerization, immutability and atomicisation: any vague gestures towards security from the aforementioned technologies are made redundant by two frameworks and invalidated by the compromised web of trust our entire world relies upon using identity as authentication.

                • MotoAsh@piefed.socialEnglish
                  0·
                  4 months ago

                  lol your ability to shit out words and demonstrate how deep your assumptions are is … hilarious.

                  The overhead on storage is hardly of consequence, especially for corporations. Otherwise even windows apps wouldn’t bundle so many dll’s next to the exe’s.

                  It’s not always about security. In larger deployed environments, even dependencies among the corporation’s own apps that they develop, let alone all apps they might need to use, might have different versions of dependencies to use. They might work with entirely different languages and frameworks.

                  Instead of loading up raw servers or VM’s with twenty external dependencies of potentially varying versions, which would quickly become a nightmare to administer, they just ship containers. Each app can do what ever the hell the team wants with what ever the hell versions of dependencies they want. It quickly becomes very important for ease of IT administration to just have little black boxes that have their defined ins and outs.

                  It’s usually much less important for an individual’s personally used computer, but it should still be easily understandable that some people do not like having to install several dependencies for one app (even when the package manager handles it 99% of the time these days). Especially if those dependencies create a lot of files here and there, or potentially interfere with other things installed. Maybe it’s as simple as an app they like requires Java 11, and they don’t want to install it across the entire OS.

                  Again, you’d have to be an absolute idiot to fail to realize that these problems and wants do exist for others.

  • Xylight‮@lemdro.idEnglish
    01·
    4 months ago

    Flatpak is a great comment ragebait source. Nativoids really be letting an image viewer access the entire filesystem and network stack

    • ninepointeight@lemmy.ml
      1·
      4 months ago

      Nativoids really be letting an image viewer access the entire filesystem

      GNOME’s default image viewer (Loupe) has full filesystem read/write access even when it is installed via Flathub. The sandbox is useless.

      https://flathub.org/en/apps/org.gnome.Loupe

      But of course, keep using buzzwords like “Nativoids” and then saying you are just ragebaiting.