

Although Hyprland in particular no longer does so.Anon-E-moose wrote:they mostly all use wlroots under the hood.
It does. And it is still wlroots based and it will be in the future. Only it ported it to C++ and integrated it into their code base. Everything wlroots works, and it should work on Hyprland. If it doesn't, it's bug.flexibeast wrote:Although Hyprland in particular no longer does so.Anon-E-moose wrote:they mostly all use wlroots under the hood.

This post from July last year says otherwise:logrusx wrote:It does. And it is still wlroots based and it will be in the future. Only it ported it to C++ and integrated it into their code base. Everything wlroots works, and it should work on Hyprland. If it doesn't, it's bug.flexibeast wrote:Although Hyprland in particular no longer does so.Anon-E-moose wrote:they mostly all use wlroots under the hood.
Have they since moved back to being wlroots-based? The following suggests they haven't:Hyprland is no longer a wlroots-based Wayland compositor, and instead, a fully independent implementation of the protocol.
Don’t worry though, all your wlroots apps will still work.
Code: Select all
$ equery g --depth=5 hyprland-0.46.2-r1 | grep wlroots
$No they haven't. If you read your own link you'll find references to what they've actually done. And it's no more different than what it has been to this day. I'll say it once again:flexibeast wrote:This post from July last year says otherwise:logrusx wrote:It does. And it is still wlroots based and it will be in the future. Only it ported it to C++ and integrated it into their code base. Everything wlroots works, and it should work on Hyprland. If it doesn't, it's bug.flexibeast wrote: Although Hyprland in particular no longer does so.
Have they since moved back to being wlroots-based? The following suggests they haven't:Hyprland is no longer a wlroots-based Wayland compositor, and instead, a fully independent implementation of the protocol.
Don’t worry though, all your wlroots apps will still work.
Code: Select all
$ equery g --depth=5 hyprland-0.46.2-r1 | grep wlroots $
Best Regards,Wlroots' wayland protocols are still supported, so apps designed for wlroots compositors will still work (just like most do work on e.g. KDE too) so you can sleep safe with regards to that.

i did in fact, read the link, and what was done. i also literally quoted Vaxry, the author of the page i linked, saying in the text at the link that "Hyprland is no longer a wlroots-based Wayland compositor", which tallies with my original comment that "Although Hyprland in particular no longer [uses wlroots under the hood]." Further, the text at the link explicitly contrasts the new code with "wlroots implementations":logrusx wrote:No they haven't. If you read your own link you'll find references to what they've actually done.
It then goes on to say:All protocol implementations are now integrated into Hyprland itself, and written with C++. This should reduce the amount of memory issues and bugs compared to wlroots implementations and has already been doing that.
That is, the new backend, 'aquamarine', is specifically distinguished from wlroots.The backend rendering stuff has been migrated into a library written from scratch called aquamarine.
Aquamarine is not a competitor to wlroots - wlroots is a library for building Wayland compositors, while aquamarine is a tiny library providing an abstraction on top of the very low-level backend stuff, that also allows your program to run on either a Wayland compositor (in a window) or on a DRM session (tty).
Code: Select all
init=/sbin/openrc-init
-systemd -logind -elogind seatdI am NaN! I am a man!