mmstick

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.