thecatvoid 2022-08-07 12:07:22
a protocol ig, but at the end of the day, wayland + wlroots can fully replace X
smol_mazunki 2022-08-07 12:57:03
i have a bunch of symlinks in my ~/.local/bin. i moved ~/.local/gits to ~/.local/src
smol_mazunki 2022-08-07 12:57:17
any tips on updating the symlinks?
smol_mazunki 2022-08-07 13:01:56
this is a good start
smol_mazunki 2022-08-07 13:08:28
looks good to me
Jamerive 2022-08-07 14:25:00
thecatvoid 2022-08-07 12:07:22
a protocol ig, but at the end of the day, wayland + wlroots can fully replace X
I hope wlroots became a standart because wayland created a mess, almost a wild west without a true consistency for the ones that makes third party apps
Jamerive 2022-08-07 14:26:48
I agree about foss blog said about wayland seems to be build to be a gnome solution only
theoooooooooooooooooo 2022-08-07 14:26:55
Jamerive 2022-08-07 14:25:00
I hope wlroots became a standart because wayland created a mess, almost a wild west without a true consistency for the ones that makes third party apps
i agree
at least everything under the xorg has something in common, but not so for wayland
there’s kwin, libmutter, wlroots
and what’s worse is, even though many wms are based on wlroots, they do not share the same properties
theoooooooooooooooooo 2022-08-07 14:27:16
hyprland has blur, while sway devs said they won’t implement it
theoooooooooooooooooo 2022-08-07 14:27:29
meanwhile in xorgland, just swap compositors and you’re fine
Jamerive 2022-08-07 14:28:02
theoooooooooooooooooo 2022-08-07 14:26:55
i agree
at least everything under the xorg has something in common, but not so for wayland
there’s kwin, libmutter, wlroots
and what’s worse is, even though many wms are based on wlroots, they do not share the same properties
at least everything under the xorg has something in common, but not so for wayland
there’s kwin, libmutter, wlroots
and what’s worse is, even though many wms are based on wlroots, they do not share the same properties
Whati s more enraging is how the wayland dev brush it off the problem
theoooooooooooooooooo 2022-08-07 14:28:30
Jamerive 2022-08-07 14:28:02
Whati s more enraging is how the wayland dev brush it off the problem
wayland dev? or the sway dev?
wayland is developed by freedesktop.org iirc
Jamerive 2022-08-07 14:30:16
theoooooooooooooooooo 2022-08-07 14:27:16
hyprland has blur, while sway devs said they won’t implement it
So imagine that as a an app maker you have to build code for 5 compositor plus windows and macos… This dev seems to favour big projects over small ones and that will smash the willness to build apps
Jamerive 2022-08-07 14:30:27
theoooooooooooooooooo 2022-08-07 14:28:30
wayland dev? or the sway dev?
wayland is developed by freedesktop.org iirc
wayland is developed by freedesktop.org iirc
Wayland devs
Jamerive 2022-08-07 14:31:30
The said, it is not our problem, we gave you the protocol, go to complain with the owners of the compositors.
theoooooooooooooooooo 2022-08-07 14:31:44
Jamerive 2022-08-07 14:31:30
The said, it is not our problem, we gave you the protocol, go to complain with the owners of the compositors.
exactly
i have seen this
theoooooooooooooooooo 2022-08-07 14:32:27
and the sway situation too is pretty worse:
i mean, like forget blur and stuff,
they could’ve just given inactive dim and lil transitions like fade
i mean, like forget blur and stuff,
they could’ve just given inactive dim and lil transitions like fade
theoooooooooooooooooo 2022-08-07 14:32:49
Jamerive 2022-08-07 14:30:16
So imagine that as a an app maker you have to build code for 5 compositor plus windows and macos… This dev seems to favour big projects over small ones and that will smash the willness to build apps
ooooof
Jamerive 2022-08-07 14:32:51
And by the way, the protocol core does not have some feature so some projects outside freedesktop created new a bunch outside the core that aren’t supported officially
Jamerive 2022-08-07 14:34:09
That means that not all compositor support that protocol extra feature so more hellish to make some apps
Jamerive 2022-08-07 14:34:53
Suppose you want blur and transitions in your app for example
Jamerive 2022-08-07 14:36:10
But wlroots does not have that… Damn… Now you have to build an especific version for wlroots… And kde and gnome and so on…
Jamerive 2022-08-07 14:36:49
And that is why the lack of apps in wayland and the reason of the poor adoption….
theoooooooooooooooooo 2022-08-07 14:37:11
Jamerive 2022-08-07 14:34:53
Suppose you want blur and transitions in your app for example
exactly,
stuff supported in libmutter aint in wlroots and so on
i have read about libmutter not supporting some feature in gtk-layer-shell but wlroots does and so on
Jamerive 2022-08-07 14:37:43
And no, xorg-wayland does not solve that because it breaks funtionality of xorg apps
theoooooooooooooooooo 2022-08-07 14:38:09
Jamerive 2022-08-07 14:36:10
But wlroots does not have that… Damn… Now you have to build an especific version for wlroots… And kde and gnome and so on…
smol_mazunki 2022-08-07 14:38:16
theoooooooooooooooooo 2022-08-07 14:26:55
i agree
at least everything under the xorg has something in common, but not so for wayland
there’s kwin, libmutter, wlroots
and what’s worse is, even though many wms are based on wlroots, they do not share the same properties
at least everything under the xorg has something in common, but not so for wayland
there’s kwin, libmutter, wlroots
and what’s worse is, even though many wms are based on wlroots, they do not share the same properties
which is half the point
theoooooooooooooooooo 2022-08-07 14:38:30
Jamerive 2022-08-07 14:37:43
And no, xorg-wayland does not solve that because it breaks funtionality of xorg apps
stuff running through xwayland
looks terrible on wayland
theoooooooooooooooooo 2022-08-07 14:38:46
smol_mazunki 2022-08-07 14:38:16
which is half the point
enlighten me, sir
smol_mazunki 2022-08-07 14:38:48
instead of working directly on the implementation, we use interfaces to request changes
theoooooooooooooooooo 2022-08-07 14:38:51
i might be mistaken
smol_mazunki 2022-08-07 14:39:23
the wayland protocol just says “yo we got wl_this_and_that which is a feature your compositor can choose to use”
smol_mazunki 2022-08-07 14:39:41
and applications can then try to use them, and it’s up to your compositor/configuration to manage it accordingly
smol_mazunki 2022-08-07 14:40:03
under xorg applications “just did whatever they wanted” which caused a headache when trying to customize stuff
Jamerive 2022-08-07 14:40:08
smol_mazunki 2022-08-07 14:39:41
and applications can then try to use them, and it’s up to your compositor/configuration to manage it accordingly
So it is a hell toward the compositor maker then?