

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.
Alpha 5 is actually releasing next week. I’d also disagree with “very alpha” as most of the beta milestone is finished now. Regardless, I don’t understand where the disconnect is. A spin can release at any time. Doesn’t matter when COSMIC Epoch 1 releases.
That would be completely wrong. See the Fedora Miracle Spin, for example. The project (miracle-wm
) is still a work in progress, and yet Fedora already officially offers a Spin for it. What you’re describing would only be true if Fedora was switching to COSMIC as the official desktop for Fedora.
There would be no reason to delay anything regardless of it being beta or not. Fedora is always doing rolling release updates of software that lends well to that paradigm, and COSMIC is one of those. It’s not like GNOME or KDE where you have to carefully and meticulously manage 100 system libraries used by the whole ecosystem. System dependencies in the COSMIC ecosystem are virtually non-existent. If they really wanted to, they could just wait a few weeks to release the spin. But I don’t think there’s any reason to.
I’d recommend spending some time reading about it. It’s not as hard as he thinks. Applications developed for Linux are quite easy to port to Redox. It supports many of the same system calls and has a compatible libc implementation. The kernel does have abstractions to ease the porting process. And if you’re going to make a new kernel today, you should do it right and make a microkernel like Redox. One of the benefits of having a microkernel is that it doesn’t matter what language you write drivers in. They’re isolated to their own processes. Rust, C, C++, whatever.
It does work like this, but as with justice, the wheels can be slow at times.
What report are you referring to?
What GPU configuration do you have? I don’t have any of these issues. If NVIDIA, you have to wait for NVIDIA to release explicit sync Wayland drivers.
I’ve seen plenty of people using GTK themes with rectangular switches.
I’d recommend everyone to try out cosmic-store
(with cosmic-icons
) 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.
Yeah, it’s in the Pop!_OS 22.04 repositories, this Fedora 40 COPR, and on the AUR.
Consumes less energy (CPU) while also rendering more responsively.
I’d just remove it with sudo apt remove pop-shop
, and install cosmic-store
(with cosmic-icons
) instead.
Pop Shop
Install the cosmic-store
(with cosmic-icons
) and try it out!
Speaking of being defensive, not only are you being far more defensive than I, but these bullet points are both misleading and wildly inaccurate. It’s also telling that you think none of my points are good, when they are the truth. Could you possibly be even more a hypocrite?
I think it already it is available on NixOS
Ubuntu is Debian with more up-to-date packages and a lot of additional third party packages. There’s a lot of companies who produce development toolkits, frameworks, and applications that are explicitly built for the Ubuntu base. Some governmental agencies and organizations also require access to packages and repositories that have been audited by security agencies, which Ubuntu has gone through the process of getting certification for certain kernels and their Ubuntu Pro repositories. All of which are useful for real world customers.
Regardless of shortcomings in Snap, Pop does not rely on Snaps, and offers its own packaging for things that would otherwise require Snap on Ubuntu.
GNOME Shell extensions are JavaScript monkey patch injections to gnome-shell’s JavaScript process. They’re only compatible with the exact version of gnome-shell that they target because most of them require to override private internals of gnome-shell that are sensitive to order of injection and names of private variables and methods.
COSMIC uses a modern Wayland-based approach to shell interface design with layer-shell applets. Each applet is its own process, using the layer-shell Wayland protocol to render their windows as shell components, and communicating with the compositor securely with the security context Wayland protocol. The protocols they use are standardized, so they will be stable across COSMIC releases. Other Wayland compositors could integrate with them if they desire to.
There’s a very large gap between having tiling, and having excellent auto-tiling capabilities with intuitive shortcuts and behaviors. COSMIC’s autotiling was designed from the ground up to be just as usable with a mouse as it is with a keyboard.
The alpha began in August of last year, and will continue to be classified as alpha until all features are finished.