cross-posted from: https://lemmy.world/post/13038090
https://fosstodon.org/@soller/112083947500126938
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.
You must log in or register to comment.
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.
And they can be packaged for any distro without a single problem
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.
You can use it with dnf and rpm-ostree too already ;D
Cosmic is a desktop environment, not a distro. So Pop!OS will keep using deb packages and something like a Fedora Cosmic Spin will use rpm packages.
