The alpha began in August of last year, and will continue to be classified as alpha until all features are finished.

I’d recommend everyone to try out cosmic-store (with cosmic-icons) when they get a chance. Whether you use COSMIC or not, it’s fully functional with any desktop environment. It’s packaged by default in Pop!_OS 22.04, available in Fedora 40 via ryanabx/cosmic-epoch, and the AUR.

Speaking of being defensive, not only are you being far more defensive than I, but these bullet points are both misleading and wildly inaccurate. It’s also telling that you think none of my points are good, when they are the truth. Could you possibly be even more a hypocrite?

If COSMIC is pathetic, then GNOME must be abysmally unusable. COSMIC was already planned long before there was any beef with GNOME. We listen to user feedback and prioritize development of features that our developers and users want. Good luck trying to replicate COSMIC’s theming and tiling capabilities in GNOME. Let alone the overall stability and performance of COSMIC. COSMIC Store is the fastest app store on Linux now. I’d recommend everyone to try it out. sudo apt install cosmic-store

How so? 22.04 is actively maintained and updated by Ubuntu, and is still the latest LTS release. On top of that, the most important packages in Pop!_OS are updated frequently, so we are on Mesa 24.0.3 and Linux 6.8.0. As for when COSMIC releases, you should read last month’s blog post.

All desktops use the Super key nowadays. Sway, i3, GNOME, Plasma, etc. are all using the Super key. Have been for years. The standard convention is that the Super key is reserved for system-level shortcuts handled by the window manager; and Alt key shortcuts are reserved for application-level shortcuts. Your desktop might have bound both Alt and Super because of legacy reasons.

You might be surprised how much disk space those GNOME Circle applications actually require, despite being dynamically linked to a lot of GTK/GNOME libraries. Unless they’re written in a scripting language, they’re much closer to a COSMIC application than you think.

• https://flathub.org/apps/org.gnome.TwentyFortyEight 12 MB
• https://flathub.org/apps/org.gnome.Reversi 12 MB
• https://flathub.org/apps/org.gnome.NetworkDisplays 13 MB
• https://flathub.org/apps/org.gnome.eog 12 MB
• https://flathub.org/apps/org.gnome.Photos 29 MB
• https://flathub.org/apps/org.gnome.Notes 12 MB
• https://flathub.org/apps/org.gnome.gedit 20 MB
• https://flathub.org/apps/app.drey.Warp 22 MB
• https://flathub.org/apps/com.github.flxzt.rnote 41 MB
• https://flathub.org/apps/io.gitlab.news_flash.NewsFlash 42 MB

I don’t see the issue with an application having a static binary within the realm of 15-25 MB. Even if you had 100 applications installed, that’s only 2 GB of disk usage.

I wouldn’t rule out the possibility of a cosmic-applets-community package which bundles third party applets, or the gradual inclusion of popular applets into cosmic-applets. Given that an applet would only become popular if there’s a lot of need for those use cases, then it would make sense to open a path to getting them mainlined.

That’s already happening

I assume you meant Pop!_OS instead of COSMIC. Pop!_OS 24.04 will be based on Ubuntu 24.04.

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 don’t think you can say that because we haven’t published our design language yet. Only a handful of design mockups have been published so far. The screenshots here are not design mockups but a work in progress implementation. Hence the “In-progress” part of the title.

Rounded corners are a user preference in the Appearance page in COSMIC Settings.

Sounds like voltage droop and/or a motherboard with faulty automatic “training” settings. I don’t recall if the Ryzen 3000 had custom PBO curves, but tweaking this can fix it. Upping LLC and the SOC and CPU voltage slightly alternatively could help. Though I’ve had my most stable overclock by disabling PBO entirely and using a manual CPU multiplier.

It’s difficult to say for sure with certainty what the issue is without trial and error. I would expect that the motherboard’s manufacturer would make sure that their board can successfully pass all tests with the standard JEDEC spec for DDR4 (2133 MHz).

Since you say that you’ve tried different RAM kits, another alternative could be the cleanliness of power from the power supply. Perhaps there is intermittent voltage droop, and you need to experiment with the Load Line Calibration settings to adjust for vdroop between idle and load. Disabling frequency boosting and manually setting the CPU frequency could help check if it’s related to that. PBO curves might be undervolting too much while idle.

That’s already not possible on GNOME because some GNOME applications hardcode their theme, others use libadwaita, some use GTK4 without libadwaita, some use GTK3, and there may still be a GTK2 app lingering around here and there in the repos (ie: GIMP).

Few people are going to care that there’s a GTK application installed on their COSMIC desktop. COSMIC will automatically generate GTK3/4 themes to match the system theme. We may even automatically generate a libadwaita theme, so it will look “same enough”.

None of what you stated makes sense. Most people are not using exclusively GNOME applications on GNOME, or exclusively KDE applications on KDE. Like with elementary OS, most people are running applications like Steam, Spotify, Discord, Zoom, Slack, etc. Plenty of people are using Qt and KDE applications on GNOME, or GTK and GNOME applications on KDE. You think no one uses Krita or Scribus on GNOME, or GIMP on KDE?

Thanks to Flatpak, you might even be running elementary applications on your system. Even Windows back in the late 90s and 2000s was full of desktop applications with custom proprietary interfaces. Nowadays everything’s becoming a web view bundled with a Chromium runtime, and you’re more worried about a COSMIC app ecosystem having a different UI from GTK?

COSMIC is a good thing because it’s a standardized and open source cross-platform native desktop toolkit. People can create themes for it, and those themes can be bundled alongside GTK and Qt/KDE themes. Due to the nature of how Rust libraries are developed and linked, COSMIC applications are mostly statically-linked, which even makes it trivial to put them on a USB drive and bring them to any PC.

I’m not sure why you think this is unique to COSMIC or elementary OS. Do you not realize that this is true of all operating systems? Look at Steam, Spotify, Discord, Zoom, and Slack for starters.

Make sure you have the latest firmware for your motherboard. This sounds like unstable voltages for memory, or an overly-aggressive PBO curve. Did you try disabling the XMP profile on the RAM, disabling PBO, and upping the voltages (within safe limits) of the SOC, DDR, and VDDP? You might find some useful info here[0] or here[1] if you intend to run your memory at 3200 MHz.

• [0] https://github.com/integralfx/MemTestHelper/blob/oc-guide/DDR4 OC Guide.md#amd
• [1] https://www.techpowerup.com/review/amd-ryzen-memory-tweaking-overclocking-guide/2.html

You can start with the libcosmic repository, and the examples contained within. We’re going to work on revamping our design demo application soon, which will be a learning resource for COSMIC application development

Git integration now in progress