It wasn't that long of a delay. Just a couple months. Also, keep in mind that this was the first release of COSMIC. Even if it had hypothetically taken an extra six months, that does not set the basis for a release cadence. There will be regular releases from this point.
GTK3, GTK4, and libadwaita applications do look native in COSMIC. In COSMIC Settings, navigate to Desktop > Appearance > Icons and toolkit theming. Or search "toolkit" and it will be a top result. In the context drawer that opens on the right, toggle "Apply current theme to GNOME apps". This will then allow the cosmic-settings-daemon to automatically generate CSS variables for GTK4 and libadwaita apps. If adw-gtk3 is installed, it will also apply those variables to GTK3 applications.
Qt4 and Qt5 applications are unsupported, but IgKh/CuteCosmic has a Qt6 Platform Theme that integrates with the cosmic theme system and applies that theming to Qt6 applications. Though it won't work in 24.04 because most of the KDE/Qt apps in this release are based on Qt5, and the version of Qt6 is too old.
I'd recommend everyone to try out `cosmic-store` 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.
What do you think a desktop environment is? Name one desktop environment that does not have its own file manager or terminal. Name and shame the platform and toolkit that lacks these basic necessities.
There are dozens of GUI libraries and platform toolkits available to both Mac and Windows. In fact, there are plenty of GTK and Qt applications floating around on these platforms. As well as a lot of applications using custom frameworks. Then of course the unfortunate web-apps-as-desktop-apps pipeline in the form of Electron. Fragmentation is a very loaded and derogatory term used to express disdain for the openness and freedom that open source desktops have. Fragmentation is a strength of open source.
Have you never heard of tiling window management? You do realize that tiling window managers are used on multi-display setups with multiple 4K displays, right? Windows have to be responsive to very narrow widths to be comfortable for use in a tile. Regardless if you have a small screen, or use 4K displays like I do.
Third party developers have access to the same APIs that COSMIC applets and applications use. It's not possible for a crate to prevent use of public APIs based on who is importing the crate.
libadwaita/GTK4 is to GNOME what libcosmic is to COSMIC.
COSMIC has no need for an alternative to GLib or GIO. Rust's standard library, the futures crates, and tokio are more than sufficient for handling I/O and asynchronous code execution. libcosmic uses tokio executors for handling application commands by default. You can bring your own executor and thread pool libraries if you want.
This is not true, and I do not know what gave you that impression. What you're describing is a side effect of using systemd-sysext, but I do not know why you would be using that.
Where the elementary appcenter needs 900 MB, and KDE Discover needs 600 MB, the COSMIC Store needs only 60 MB. The COSMIC Store uses serde to serialize package metadata into a bitcode format, which uses significantly less memory and enables rapid application startup times. As a result, it does not need to run in the background, and it can search the entire database in realtime within 5ms.
VRR, fractional scaling, and 10-bit color depth is already supported. HDR metadata is not yet supported. These will be refined before the final release.
See also our first four COSMIC applications with the default dark and light themes[0]: a terminal, file manager, text editor, and settings application. SavvyNik also demoed a slightly older build of these applications in a recent video today[1].
That's just not how software development works. The quality of the software depends on the people who own the development of that software, and the technologies they used to build that software. You're advocating that COSMIC should be a hodgepodge of random projects built with completely different frameworks with conflicting design philosophies. The end result of this is the exact opposite of good quality.
The desktop environment plays a major role in application defaults. Can you imagine installing GNOME and getting Kate as the text editor, bundled with all of its KF5 libraries? Or installing KDE and getting GNOME Text Editor bundled with libadwaita and GNOME libraries? That's what you're asking us to do with COSMIC. Which is insane because it's not that difficult to make a text editor when you have a mature platform toolkit.
A desktop environment is more than a window manager. Can't remember installing a DE and not having a platform default text editor included as a core application.
The text editor is being developed solely by our principal engineer thus far. Application updates may be the most visually interesting thing to share in an update, but it's far from the only thing being worked on. A default text editor doesn't need to be complex, and if you look at the source code, it's very lean and readable. It's a fun side project that tests our platform toolkit, and not at all taking anything from development of the cosmic compositor or its applets.
Lots of them. I've read a lot of comments from the Rust community that they'd love to build native applications in Rust. This will be their moment to make something as C programmers had with GNOME, and C++ programmers had with KDE.
It's been only a little more than a year since it was started. I don't know anyone who's able to announce the start of development of a new DE, and then have it released in less than a year.