Yeah, the author normally rarely misses an opportunity to complain about KDE being too complex in his articles - and COSMIC aims to fall in that sweet spot between the extremes that are GNOME and KDE, while adding features like optional but native tiling.
The applet concept where applets live in their own process and communicate via Wayland protocols (behind a COSMIC API) is also less likely to break than GNOME plugins that are horribly injected into its bowels.
Given the toolkit, organized development and UX decisions being up-front designed with figma sketches, etc. that are reviewed before implemented, and having both paid developers and community contributors it has a lot of potential.
Wayland compositors use IPC over a UNIX socket to communicate with Wayland clients. To increase security and enable sandboxed applet support, COSMIC applets use the security-context protocol for their IPC connection to the compositor. To be an applet, COSMIC applications use the layer-shell protocol to behave as an applet. Neither of which were made for COSMIC. Some other Wayland compositors support these protocols. You can see which compositors support the protocols at the bottom of the wayland.app protocol pages.
Yeah, the author normally rarely misses an opportunity to complain about KDE being too complex in his articles - and COSMIC aims to fall in that sweet spot between the extremes that are GNOME and KDE, while adding features like optional but native tiling.
The applet concept where applets live in their own process and communicate via Wayland protocols (behind a COSMIC API) is also less likely to break than GNOME plugins that are horribly injected into its bowels.
Given the toolkit, organized development and UX decisions being up-front designed with figma sketches, etc. that are reviewed before implemented, and having both paid developers and community contributors it has a lot of potential.
Even better. A COSMIC API was not necessary since Wayland protocols already exist for this (layer-shell and security-context).
Could you explain a little more on that? Just curious.
Wayland compositors use IPC over a UNIX socket to communicate with Wayland clients. To increase security and enable sandboxed applet support, COSMIC applets use the security-context protocol for their IPC connection to the compositor. To be an applet, COSMIC applications use the layer-shell protocol to behave as an applet. Neither of which were made for COSMIC. Some other Wayland compositors support these protocols. You can see which compositors support the protocols at the bottom of the wayland.app protocol pages.