COSMIC: The Road to Alpha
COSMIC: The Road to Alpha
blog.system76.com COSMIC: The Road to Alpha
Introducing COSMIC Terminal, and what’s left on the roadmap for COSMIC DE?
47 comments
-
I've been following the work on COSMIC (though not super actively) and I keep on saying that I like what I'm seeing because, well, I do! The idea of a tiling DE is a very exciting one and COSMIC really has the potential to become a Major Linux DE.
-
I particularly like that, just like their current Gnome extension, it supports both tiling and floating, with a quick toggle between them.
This'll be a pretty interesting year for people interested in DEs.
-
As a regular i3 user, I was very satisfied on how tiling was implemented into the Pop shell of Gnome. After a few keybind change here and there it almost felt like home maneuvering the windows and workspaces. One minor complain is glitches happen when external monitor is connected/disconnected on the fly (laptop usecase), in which case windows are disoriented and thrown around at random unexpected places instead of staying at where they were. I'm blaming Gnome on that one however, since I'm assuming it is related on how Gnome handle multiple screens and Pop shell act on top of it, so I'm expecting it to be fixed in Cosmic DE
-
-
I'm just happy there's a rust DE being written in slint. KDE is nice and all, but it's all C++. No way am I touching that trainwreck of a language again.
-
Yeah, I’m a Pop user and like what they do with Gnome now. I can’t wait to see what it’s like when the desktop isn’t limited by the Gnome extension system.
-
-
I've been following Cosmic and really looking forward to it. I love the idea of a Gnome-like desktop without Gnome-like design decisions.
-
Incredibly excited to try it. I love the early support for Nix, I plan to run it as soon as a NixOS module becomes available!
Huge props to the design team here, the aesthetic looks amazing on all of the apps I've tried. They all feel consistent and look great.
-
[cosmic-randr] uses the wlr output configuration Wayland protocols.
Does this mean cosmic-randr should work on other compositors that support the wlr output configuration protocol (e.g. sway, hyprland, river, ...)? It's great to see cosmic adopting existing protocols, instead of compositor specific protocols (or worse, no external app support at all).
Also, it's great how portable Cosmic DE seems to be, as it's already mostly packaged on NixOS. On first look, cosmic-term seems to be a quick terminal so I might switch to it, as well as cosmic-files.
-
If they support the wlr output configuration protocols, then yes it'll work fine. There are some more advanced features that we want that aren't supported by the protocol though, so we will likely develop some cosmic protocol extensions for those features.
-
-
Tldr: New desktop environment designed for PopOS (but usable elsewhere)
-
I’m really excited to test the Alpha, it’s looking really good so far!
-
It doesn't use GTK does it?
-
No, we have been making our own platform toolkit (libcosmic), which is built upon iced-rs. We are using this both for our wayland compositor applets, and our desktop applications.
-
Beautiful, so there's a good chance for it to not be a hot mess! Looking forward to it. 😊
-
iced? Interesting. I though it's still pretty experimental. There's no official documentation yet, right? When I was looking at Rust UI libraries Yew and Leptos looked more mature. I guess you're confident iced have enough backing and isn't going anywhere.
How do you find working in Rust on a bigger UI project? Any issues?
-
-
-
Just curious, on a scale from cowsay to MS Word, how difficult would it be to port COSMIC to the BSDs, assuming wayland support?
-
As long as you have access to the latest version of Rust, porting would be somewhere near cowsay.
-
-
I recognize this is an odd comment to make, but I'm glad to see this screenshot tool supports capturing a window in Wayland. My next question is, can the screenshot tool be invoked from the command-line or via a script?
-
Why do we invent new DEs instead of making proper settings app in already existing ones?
-
Because that's not how software development works, and that's not how you make progress in the field. In order for our technical vision to be integrated with an existing desktop, such as GNOME, it would have required that they give us the reigns to their project to delete their entire codebase and rebuild it into exactly what you see today in COSMIC.
As in life, sometimes you've got to demolish, pave, and build better foundations. There's a lot of cool technologies available to build a truly next-generation desktop experience in, but you're not going to get it through rigid bureaucracy and old tools. With COSMIC, we've got freedom to make decisions and build something truly unique, and we're using our talent to show you what we can do.
-
Sometimes it's easier to start over than unbreak an existing project. Gnome is old and big so it's harder to change. So starting over where you don't have to keep existing features or care about existing users is way easier than fixing gnome and rewriting it in rust. Plus system 76 can. There's no single party that can stop them from making a desktop
-
We do what we must because we can.
FOSS software development is very much like evolution. Many projects are born but only the best thrive. It is a wasteful system because resources are spread over similar projects, but it creates very good software.
-
Welcome to FOSS lol
-
Because some developers act on their own consciousness and don't have a slavemaster corporate manager telling them what they need to do or not do.
When one doesn't like any of the available choices yet a new one is born. Can you measure how many v.terminals we have, or how many window managers on X11?
-
Fortunately such "new choices" get abandoned very quickly. Making new solution instead of improving existing ones is counterproductive. Unless there is a large legacy codebase. Smart people have invented Unix principles to avoid that.
-
-
47 comments