I know this is a meme, but in case it’s has a serious undertone, the question in this case is - who really cares?
Those are desktop files. You usually don’t manually look into that folder in the terminal. It’s not like a snap where your lsblk output is being cluttered.
This is such a minor problem that it’s barely worth being talked about. It’s a mere “best practice was ignored” case that has Z E R O impact on performance, maintainability or usability.
That would be a valid complaint, however, I just installed krita for testing on arch running with KDE and there’s only one entry.
However, there’s also only a single krita entry in the list of .desktop files so idk what exactly is going on there. Maybe under KDE, it behaves differently, no clue.
It won’t show up there because the files have NoDisplay set to true, which hides them from the desktop app view, but they still show up in other places. Here’s Nautilus’ open with dialogue (where I noticed this):
They says it’s freedesktop standard, and gnome is at fault for not implementing the standard properly. I don’t have this issue in KDE. I don’t understand what it meant different files are supported by different plugins, but maybe internals depend on that structure.
Anyway gnome should be supporting that standard everywhere in all their apps
I honestly agree with the GTK devs here. The app chooser isn’t what was meant by the spec and it should show all the apps available to the user. And if KDE respects NoDisplay in the app chooser, but still shows it if the MimeType matches, then I think that’s an even more conjectural reading of the spec.
I would like to see what are differences in content for thoose different desktop files. Is there any difference in launch options? Do they contain mimetype feilds? It seems like specification explicitly states it(Nodisplay) being useful for mime types so it probably is expected feature within the spec. Also spec says nodisplay should hide from “menus” which i’m not sure if its just app launcher or all menus
The argument I see all over here (from kde side) is that support for mimetypes are optional plugins, and within the spec making multiple desktop entries is the only choice when doing so.
Okay but that would mean you have to open /etc/share/applications in a file explorer which you - usually - don’t really do. Or maybe I’m just too much of a terminal guy to do it.
I’m not sure about this case because I don’t use flatpak that much, but to be honest I hate when I install an Electron based program such Freetube, and even though I installed the BIN binary (arch btw, not happened this on Debian based distros) for some reason my package manager decided to install the whole Electron framework with DE included. I get that it depends on it to work, but I don’t need 40 Electron packages to show in my Wofi that I would never use, is so ugly. The same with Qt programs and any single KDE app (but I understand in this case)
I mean, yeah I understand that Freetube depend on Electron to work, but why when installing Steam this is not the case?
but why when installing Steam this is not the case?
Because steam has no application-dependencies, it bundles everything into one binary, including the electron binary, and ships everything in one go. However, steam still has system-dependencies that have to be installed and will pop up in rofi.
I don’t know if you’re ragebaiting or are just a massive fucking asshole tbh, but when someone develops an application for free and for fun for anyone to use, I’m not complaining about too many fucking .desktop files.
If that’s the case, that would be a fair complaint that should be fixed, but I can’t really reproduce any problems on KDE or XFCE. Then, it should also be reported as a bug so they’re aware.
While I agree that the seva should have looked out for it in the first place I think it being volunteer work and open source you or anybody else that has the time and knowledge could fix it too and give back. If it’s indeed easily solvable.
It doesn’t mean it is free that it has to be mediocre. I also do work for “free and fun” and I don’t see it as a reason to take a shit on my project. Either accept criticism or just keep the damn code for yourself.
I know this is a meme, but in case it’s has a serious undertone, the question in this case is - who really cares?
Those are desktop files. You usually don’t manually look into that folder in the terminal. It’s not like a snap where your
lsblkoutput is being cluttered.This is such a minor problem that it’s barely worth being talked about. It’s a mere “best practice was ignored” case that has Z E R O impact on performance, maintainability or usability.
My application menu did get cluttered with multiple krita entries.
Which was a minor annoyance.
That would be a valid complaint, however, I just installed krita for testing on arch running with KDE and there’s only one entry.
However, there’s also only a single krita entry in the list of .desktop files so idk what exactly is going on there. Maybe under KDE, it behaves differently, no clue.
It won’t show up there because the files have
NoDisplayset to true, which hides them from the desktop app view, but they still show up in other places. Here’s Nautilus’ open with dialogue (where I noticed this):https://bugs.kde.org/show_bug.cgi?id=403194
They says it’s freedesktop standard, and gnome is at fault for not implementing the standard properly. I don’t have this issue in KDE. I don’t understand what it meant different files are supported by different plugins, but maybe internals depend on that structure.
Anyway gnome should be supporting that standard everywhere in all their apps
https://gitlab.gnome.org/GNOME/gtk/-/work_items/7776#note_2560841
I honestly agree with the GTK devs here. The app chooser isn’t what was meant by the spec and it should show all the apps available to the user. And if KDE respects
NoDisplayin the app chooser, but still shows it if theMimeTypematches, then I think that’s an even more conjectural reading of the spec.I would like to see what are differences in content for thoose different desktop files. Is there any difference in launch options? Do they contain mimetype feilds? It seems like specification explicitly states it(Nodisplay) being useful for mime types so it probably is expected feature within the spec. Also spec says nodisplay should hide from “menus” which i’m not sure if its just app launcher or all menus
The argument I see all over here (from kde side) is that support for mimetypes are optional plugins, and within the spec making multiple desktop entries is the only choice when doing so.
Okay but that would mean you have to open /etc/share/applications in a file explorer which you - usually - don’t really do. Or maybe I’m just too much of a terminal guy to do it.
This isn’t a directory, it’s the list of apps that show up when you right click a file and select ‘Open With’.
I’m not sure about this case because I don’t use flatpak that much, but to be honest I hate when I install an Electron based program such Freetube, and even though I installed the BIN binary (arch btw, not happened this on Debian based distros) for some reason my package manager decided to install the whole Electron framework with DE included. I get that it depends on it to work, but I don’t need 40 Electron packages to show in my Wofi that I would never use, is so ugly. The same with Qt programs and any single KDE app (but I understand in this case)
I mean, yeah I understand that Freetube depend on Electron to work, but why when installing Steam this is not the case?
Because steam has no application-dependencies, it bundles everything into one binary, including the electron binary, and ships everything in one go. However, steam still has system-dependencies that have to be installed and will pop up in rofi.
I guess it depends of a bunch of things, but why when programmers package a program don’t do the same more often?
You’re encouraging mediocre work
I don’t know if you’re ragebaiting or are just a massive fucking asshole tbh, but when someone develops an application for free and for fun for anyone to use, I’m not complaining about too many fucking .desktop files.
Apparently it causes issues with “Open With” menu entry spam in some DEs. It’s a minor issue but easily solvable and it impacts usability.
If that’s the case, that would be a fair complaint that should be fixed, but I can’t really reproduce any problems on KDE or XFCE. Then, it should also be reported as a bug so they’re aware.
Agreed
While I agree that the seva should have looked out for it in the first place I think it being volunteer work and open source you or anybody else that has the time and knowledge could fix it too and give back. If it’s indeed easily solvable.
It doesn’t mean it is free that it has to be mediocre. I also do work for “free and fun” and I don’t see it as a reason to take a shit on my project. Either accept criticism or just keep the damn code for yourself.
Yeah you’re ragebaiting good one lmao