It is normal for cosmic applications to write logs to the terminal.

You have to type the key sym name into the input field. It is not a raw shortcut editor yet.

You are already on the LTS version if you’ve installed the COSMIC Alpha 6 ISO, or did a release upgrade.

You can choose a session in cosmic-greeter through a dropdown.

You don’t have to watch. You can listen to it in the background.

It’s really easy to configure a self-hosted forgejo instance. Even if you rm your local work, you can clone it from your server. Be that hosted on the same system over localhost, or on another system in your network.

3D acceleration is required with cosmic-comp right now. I’m not sure if software rendering will be ready or not for the first release, but it is on the issue board.

There’s already been explanations in every thread on COSMIC for the last 2 years. Along with a dozen interviews and conference talks. Why are you demanding answers here?

See the Ubuntu Summit 2024 talk: https://www.youtube.com/watch?v=bwrBKccfYws

It’s not resources, in fact, this Alpha performs pretty poorly on its own vs Gnome

I haven’t seen any benchmark where GNOME was more performant than COSMIC. Despite alpha status, it is already much more responsive than GNOME.

GNOME uses a single thread to render all displays in a multi-display configuration. This is often so slow that they need to rely on double or even triple buffering when the frame rate lags behind the display’s refresh rate. Meanwhile in COSMIC, thanks to the thread safety features of Rust, it was easy to implement thread-per-display multi-threaded rendering. This means that each display is rendered and composited independently on their own respective threads.

GNOME’s compositor also has an entire JavaScript runtime bundled inside of it, which it uses for drawing interfaces and handling application logic for those interfaces. All within the same process as the compositor, slowing down its event loop. COSMIC instead keeps the compositor process very lean, with all desktop interfaces running in their own isolated processes outside of the compositor via wayland’s layer-shell protocol.

If you can’t see the difference, it’s because you’re not even looking.

It can’t be fixed without forking and rewriting a lot of gnome-shell’s internal logic.

Also, COSMIC is not a rewrite of GNOME. Not even close. It is a completely different architecture, toolkit, language, and design system.

deleted by creator

Doesn’t matter. New compositor: cosmic-comp. Does not share any code with gnome-shell or mutter.

OpenGL is required, even if by software rendering.

No modifications are being done to Qt/KDE theming, and we won’t be able to get KDE apps to adapt to the COSMIC theme until the KDE ecosystem has finished migrations to the Union theme engine.

I don’t know how you can keep telling me that I never contacted Canonical even though I did. Nor did anyone ever publicly mock Canonical. You are putting words in our mouths. So much contradictory and hyperbolic nonsense here. Let me guess: you read a certain hyperbolic hit piece from a Chris Davis—one of the most prominent libadwaita and stopthemingmyapp developers—whom had a personal axe to grind with us because of many heated online arguments with him over the petition, theming, and libadwaita. He created a hit piece to influence public perception of the company and intentionally used the GNOME blog to reach the widest audience for his vendetta. Even though if you dig through the details his statements are weak, if not outright false. To make matters worse, GNOME never addressed that personal blog post hosted on their website, even though we had been sponsoring and sometimes hosting GNOME events for 5 years prior, and donated a total of $100K. Leading many to conclude that this was the voice of GNOME, even if internally it was not. This is what happens if you only read the story from one side without putting equal weight on the other.

You can’t release a desktop operating system without a file manager or text editor. The xdg desktop portal interface for the file chooser portal dialogs requires a file manager to be implemented for the portal to be able to create a file chooser dialog for the operating system on behalf of applications requested file choosers through the portal.

The text editor is also required to have a GUI toolkit featuring properly rendered and editable text. It is thanks to the text editor project that the Rust ecosystem now has cosmic-text as the de facto crate for handling text layout, shaping, and rendering with support for international language glyps, ligatured language scripts, and bidirectional text layouts.

Virtual machines have always been supported as long as you enable GPU acceleration. GNOME Boxes, virt-manager, and VirtualBox have been tested.

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

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