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
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.
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.
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.
Yep, just full-throatedly out here yelling how you don’t understand the problems being addresed…
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.