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.
Let him do his thing and investigate Pop on your own.
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.
Development began mid-December, using the work we already did for cosmic-edit as a template. COSMIC Terminal uses the alacritty library, but the frontend interface is designed with our platform toolkit (libcosmic), with full support for bidrectional text and ligatures because we use cosmic-text instead of freetype.
https://fosstodon.org/@soller/111602927867586005
You can see above that between alacritty, cosmic-terminal, and gnome-terminal; cosmic-terminal was the only terminal to render correctly. Since then, we've given it the COSMIC treatment and now we have a tabbed interface with settings, search, etc.
https://fosstodon.org/@soller/111733526892594130
We're still in the process of designing and implementing features, but don't hesitate to try it out!
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.
NVIDIA believes they'll have the Vulkan on Wayland issue fixed in the 550 driver that they are planning to release early this year. Someone's working on a fix in wgpu that happens to also boost performance for every driver in demos.
We've been using COSMIC on our systems since summer of last year. Some graphics drivers have issues, particularly NVIDIA drivers using Vulkan on Wayland. There are some XWayland bugs from time to time. It is very usable as is, but some settings aren't implemented yet, and some toolkit features aren't fully implemented.
Make sure to report issues on GitHub with details so we can investigate it when we have time.
Me: Can we have COSMIC?
Mom: We have COSMIC at home.
COSMIC at home: Attempting to call back into JSAPI during the sweeping phase of GC. Stack trace for context
Joking aside, COSMIC is nothing like GNOME. Not visually, not feature-wise, nor is it using the same software stack. It is as close to GNOME as KDE is to GNOME. Developed from the ground up in Rust.
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.
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.