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
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.
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.