mmstick

joined 2 years ago
MODERATOR OF
[–] mmstick@lemmy.world 1 points 3 days ago

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

[–] mmstick@lemmy.world 3 points 1 week ago (5 children)

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

20
submitted 1 week ago* (last edited 1 week ago) by mmstick@lemmy.world to c/pop_os@lemmy.world
[–] mmstick@lemmy.world 3 points 3 weeks ago (1 children)

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.

[–] mmstick@lemmy.world 1 points 4 weeks ago

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?

[–] mmstick@lemmy.world 6 points 4 weeks ago* (last edited 4 weeks ago)

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.

[–] mmstick@lemmy.world 2 points 4 weeks ago

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

[–] mmstick@lemmy.world 2 points 4 weeks ago* (last edited 4 weeks ago)

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.

[–] mmstick@lemmy.world 2 points 4 weeks ago (3 children)

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

[–] mmstick@lemmy.world 1 points 4 weeks ago (5 children)

OpenGL is required, even if by software rendering.

[–] mmstick@lemmy.world 2 points 1 month ago (1 children)

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.

[–] mmstick@lemmy.world 3 points 1 month ago* (last edited 4 weeks ago) (1 children)

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.

view more: next ›