COSMIC Store is coming along quickly, though there is still a lot left to do. It loads nearly instantly, because it uses bitcode to cache appstream data in an optimized format. It uses very little memory compared to the Pop Shop. Searches can be performed live as they are done in parallel. Searching for "e" takes 5.5 ms on my desktop and returns 4601 results.
Not sure how long this will last, but here are some videos I took of it, try not to mind the crunch on the last one, I had to use qsv_vp9 for it since I was running out of time and space. Also don't mind the fist video's bad fps, I was compiling in the background and forgot.
Im very happy with how responsive its being in general. Discover and gnome's store are actually really sluggish to use when scrolling through in low end hardware and this app is smooth as silk.
First impressions is I'm shocked by just how fast it is, Aside from the first boot which for some reason doesn't propagate apps and needs a reboot, it's extremely fast, Gnome software and Discover aren't even within the same league of responsiveness and speed. I didn't showcase Discover since I don't know where the cache files are to delete them.
Touchscreen for sure I wish was handled better. you can see I accidentally clicked an app in the last video instead of scrolling, but thats something that I assume will be fixed with time.
This is not relevant to this specific post but does anyone know how if the static linking used in Rust is an issue with cosmic?
The last time I tried building a small app with Iced it was pretty bing (20MB) even though it didn't do much. On the other hand a GTK app in rust easily fits within 5MB.
Anyway I'm thrilled to try cosmic out as soon as it reached the Arch repos.
Static linking is not an issue. Binaries may require more space on disk, but the benefit is that they are self-contained, portable, with excellent performance, and low memory usage.
Binaries are compiled with LTO, so unused functions are stripped from the binary. What remains is highly optimized to that application's use cases.
I just realized that I haven't read any infos about the package manager that Cosmic is going to use. Is it going to be build on top of Ubuntu like Pop!OS and use apt? Are the apps going to be served by the package manager or as Flatpaks? If the later, it could be interesting to public them on the Flathub Beta remote when they reach that stage.
PackageKit isn't a package manager in the same sense as what I meant. It's more like a one level above "front end" to be able to manage different package managers with the same program. This means that "Software Stores" that use packagekit like Gnome Software or KDE Discover will work on most Linux system with whatever package manager is used in the backend. For example on a Fedora Workstation, packagekit makes it possible to install, update and manage both rpm installed through dnf, Flatpaks and if I wanted, Snaps, while on a Debian based system it would be able to manage your apt stuff, or on Arch packages installed through pacman for example. But from what I heard this also makes it a somewhat clunky and slow piece of software that has become kind of clunky and hard to maintain over the years, so its also an interesting question whether Cosmic is going to use it.