I really, really love #Gnome, but Gnome Software should be rewritten from scratch. I mean, I can use the CLI, but computer iliterate poeple should be able to use their computer without.
what would rewriting from scratch accomplish? Just a bunch of new issues. Have you considered that maybe the problems space is *hard*, and that there's no naive approach to loading a lot of data coming from multiple sources?
@ebassi But that shouldn’t take more minutes. Why is it so much slower than doing `flatpak update; sudo dnf up`.
Also loading of the categories is still very slow despite also the effort to make it more performant. That leads me to the conclusioin that something is fundamentally wrong with it.
But sure, I don’t know the code base and rewriting it could lead to the same problems.
why shouldn't it take "minutes"? Do you know what is it doing? Have you profiled it?
The CLI tools don't access the whole repository information—they don't need icons or long descriptions, or other stuff, so it's pointless to compare them to a GUI that will need to show everything.
The work to make things more performant implied rewriting a bunch of code; it's not the code that is the problem: it's the scope and user expectations.
@ebassi While I don't think that a complete rewrite of the Software app is the way to go it is important to understand that it's the only app store with such problems. KDE Discover/Google Play/Apple Store even the Microsoft store loads a lot faster
@ebassi Not being a developer, I didn't go and look at the code, which I wouldn't be able to understand. On the other hand, I get the impression that there's really no caching. For example, if I launch the application and click on the Create category, it takes a long time to load the data. If I go back and choose another category, it takes a while to load again. okay.
Emmanuele Bassi
in reply to user8e8f87e • • •user8e8f87e
in reply to Emmanuele Bassi • • •@ebassi But that shouldn’t take more minutes. Why is it so much slower than doing `flatpak update; sudo dnf up`.
Also loading of the categories is still very slow despite also the effort to make it more performant. That leads me to the conclusioin that something is fundamentally wrong with it.
But sure, I don’t know the code base and rewriting it could lead to the same problems.
Emmanuele Bassi
in reply to user8e8f87e • • •why shouldn't it take "minutes"? Do you know what is it doing? Have you profiled it?
The CLI tools don't access the whole repository information—they don't need icons or long descriptions, or other stuff, so it's pointless to compare them to a GUI that will need to show everything.
The work to make things more performant implied rewriting a bunch of code; it's not the code that is the problem: it's the scope and user expectations.
user8e8f87e
in reply to Emmanuele Bassi • • •@ebassi Maybe I need to look into profiling to make a more informed complaint.
Don’t think that the user expectations are the problem here though, as I think these problems are solvable.
Gloopsies
in reply to Emmanuele Bassi • • •While I don't think that a complete rewrite of the Software app is the way to go it is important to understand that it's the only app store with such problems. KDE Discover/Google Play/Apple Store even the Microsoft store loads a lot faster
Okki
in reply to Emmanuele Bassi • • •Not being a developer, I didn't go and look at the code, which I wouldn't be able to understand. On the other hand, I get the impression that there's really no caching. For example, if I launch the application and click on the Create category, it takes a long time to load the data. If I go back and choose another category, it takes a while to load again. okay.