Iced is a lower level GUI library, similar to what GDK is to GTK. We built our own COSMIC-themed GUI toolkit around iced, which is called libcosmic. As we’ve gotten more and more widgets and application logic developed, actual application development with libcosmic is a breeze. Even if you do have to create a custom widget, it’s much easier to creating custom widgets in GTK. We’re able to develop much faster than we ever could with GTK now.
Yew and Leptos aren’t comparable since they’re not native GUI toolkits. These are for web developers rather than application development. It wouldn’t be possible to use this for developing layer shell applets for COSMIC, either.
It’s been explained 100 times ad nauseam over the last two years. Go read comments from previous months’ updates if you want to catch up.
As for cross-platform compatibility, this should not come as a surprise because everything is written in Rust, and the libraries we use are already cross-platform by default in most instances. Supporting multiple platforms takes almost zero effort on our part. Especially when we could design something from the ground up that’s easy to adapt.
Make sure you have the latest firmware for your motherboard. This sounds like unstable voltages for memory, or an overly-aggressive PBO curve. Did you try disabling the XMP profile on the RAM, disabling PBO, and upping the voltages (within safe limits) of the SOC, DDR, and VDDP? You might find some useful info here[0] or here[1] if you intend to run your memory at 3200 MHz.
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.
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.
They commented on their video that it was their fault. There was never a packaging issue. The issue was that we pushed a systemd source package update to Launchpad, which silently didn’t build or publish the 32-bit systemd library packages, because Ubuntu had systemd on a blacklist for 32-bit package builds. We noticed this minutes after packages were published, and had it fixed within an hour later.
This didn’t actually affect any systems in the wild because apt held back the update until we had worked around the restriction on Launchpad (there was an invisible ceiling to the package version number). They were only affected during that time period because they manually entered that sentence from the prompt in a terminal. We stopped using Launchpad with 21.10, so all packages released since then are the same packages that are built and tested by our packaging server, and used by our QA team internally.
The drama and reputational damage that LTT caused was unnecessary. Especially given that they uploaded this video a week later, and never attempted to reach out. They still have yet to properly edit the video.
You are misunderstanding the data. It is not the number of users, but a percent of posts to ProtonDB, which only applies to PC gamers. There can be a disproportionately larger number of reports from those who need to spend time tweaking their system as opposed to using it, or that are particularly vocal about sharing their tweaks.
The total number of users playing games on Linux is rising each year. Pop!_OS was the first OS that a lot of people tried a few years ago, and so you’ll see a lot more diversity in choice now. People who are new to Linux, yet particularly heavily invested in it, tend to like to try out a lot of different distributions in the following years.
I’m defining it the same way that Mint and Ubuntu is here. Which is when they release a new version of their ISO. We are currently on 22.04.37. Release date January of 2024. There are substantial changes since the first ISO build of 22.04
It’s not stable in the Debian sense. We’ve always had rolling release updates for the system base; and people often complain about regressions in Linux, Pipewire, Mesa, and NVIDIA updates. I get them packaged shortly after they’re released. As long as they pass QA tests in the System76 hardware lab, they get released within a week.
I am still actively maintaining Pop!_OS. COSMIC has not changed that aspect of my job. Just within the last week I packaged Linux 6.6.8, Mesa 23.3.2, Just 1.22, Rust 1.75.0, and updated Popsicle’s dependencies to fix a bindgen build error with recent versions of Clang. We have a systemd update that was packaged today, and I’ll be doing another linux-firmware backport soon. So I don’t understand why you’d think it is stagnant. We’re even shipping Pipewire 1.0.0 by default, which Ubuntu hasn’t yet done in the latest version. People usually complain that we update too often.
There are new versions released every two or three weeks. I’m about to release Linux 6.6.8 with Mesa 23.3.2. We have Pipewire 1.0.0 and NVIDIA 545. ISOs are regularly rebuilt with our latest updates.
2022 was only a year and a half ago, and we ship the latest Linux kernel, firmware, Mesa libraries, NVIDIA drivers and libraries, Pipewire/Wireplumber, ZFS, Firefox, Alacritty, Lutris, Steam, and Rust. Since when did we start considering that to be “incredibly ancient”? The next LTS release is not yet available to base Pop!_OS upon, but we ship newer kernels and drivers than the latest version of Ubuntu.
You can start with the libcosmic repository, and the examples contained within. We’re going to work on revamping our design demo application soon, which will be a learning resource for COSMIC application development