In practice, because Rust libraries are always statically-linked, the MPL-2.0 is equivalent to the LGPL in spirit. Meanwhile, because of the static linking restrictions in the LGPL, the LGPL is effectively no different from the GPL. Hence, you’re going to find a lot of open source copyleft projects from the Rust ecosystem preferring either GPL or MPL-2.0, where MPL-2.0 is used in libraries where LGPL would have used previously in C projects. Dynamic linking is essentially going the way of the Dodo.

The Linux kernel already allows proprietary modules via DKMS, and a handful of vendors have been using this for decades, so this is no different. Case in point: NVIDIA driver, and Android vendor drivers.

All source code in Rust is statically-linked when compiled, which thereby renders the LGPL no different from the GPL in practice. For Rust, the MPL-2.0 is a better license because it does not have the linking restriction.

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.

Yeah, it’s in the Pop!_OS 22.04 repositories, this Fedora 40 COPR, and on the AUR.

Pop Shop

Install the cosmic-store (with cosmic-icons) and try it out!

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.

How so? 22.04 is actively maintained and updated by Ubuntu, and is still the latest LTS release. On top of that, the most important packages in Pop!_OS are updated frequently, so we are on Mesa 24.0.3 and Linux 6.8.0. As for when COSMIC releases, you should read last month’s blog post.

Did you not read the blog update? That is exactly what the blog update covered… The user’s theme colors are applied to the Adwaita theme used by GTK4/libadwaita, and GTK3 theme support is provided by adw-gtk3.

Are you interested in contributing? You can find the source code for theme generation here and here.

All desktops use the Super key nowadays. Sway, i3, GNOME, Plasma, etc. are all using the Super key. Have been for years. The standard convention is that the Super key is reserved for system-level shortcuts handled by the window manager; and Alt key shortcuts are reserved for application-level shortcuts. Your desktop might have bound both Alt and Super because of legacy reasons.

You might be surprised how much disk space those GNOME Circle applications actually require, despite being dynamically linked to a lot of GTK/GNOME libraries. Unless they’re written in a scripting language, they’re much closer to a COSMIC application than you think.

• https://flathub.org/apps/org.gnome.TwentyFortyEight 12 MB
• https://flathub.org/apps/org.gnome.Reversi 12 MB
• https://flathub.org/apps/org.gnome.NetworkDisplays 13 MB
• https://flathub.org/apps/org.gnome.eog 12 MB
• https://flathub.org/apps/org.gnome.Photos 29 MB
• https://flathub.org/apps/org.gnome.Notes 12 MB
• https://flathub.org/apps/org.gnome.gedit 20 MB
• https://flathub.org/apps/app.drey.Warp 22 MB
• https://flathub.org/apps/com.github.flxzt.rnote 41 MB
• https://flathub.org/apps/io.gitlab.news_flash.NewsFlash 42 MB

I don’t see the issue with an application having a static binary within the realm of 15-25 MB. Even if you had 100 applications installed, that’s only 2 GB of disk usage.

That is to show the icon theme feature.

I wouldn’t rule out the possibility of a cosmic-applets-community package which bundles third party applets, or the gradual inclusion of popular applets into cosmic-applets. Given that an applet would only become popular if there’s a lot of need for those use cases, then it would make sense to open a path to getting them mainlined.

Wayland compositors have to implement the whole display server, including special handling of XWayland windows. XWayland windows can be very finicky and require caution to handle.

The editor is meant to be a regular text editor. If you want a code editor, there is https://lapce.dev/

1. That’s not implemented, but you can click the maximize button, or press Super+M to toggle maximization.
2. You can open the Appearance settings page and change that to your preferred color scheme. We’ve already selected our default colors and they’re not going to change from here on out.
3. What do you mean by minimal? The PrintScrn key opens the screenshot utility, which lets you choose between capturing a selected region, a specific window, or the whole display
4. What’s wrong with the file manager and editor? You can use whatever editor and file manager you want, so that shouldn’t be a blocker for daily use.
5. This can be configured in the cosmic comp config, but will be implemented in the settings app soon.
6. Super+W opens the workspaces view
7. Your distribution should make sure pop-launcher is installed, and each of its plugins symlinked.
8. That is already possible in the Desktop and Panel settings page. As you can see, I’m not using a GNOME style panel or dock here.