Hyprland Goes Fully Independent From Wlroots

It's been a work in progress for quite a while now but the Hyprland developer has been working on taking the project off of Wlroots and onto a port written in C++.

==========Support The Channel==========

==========Resources==========

=========Video Platforms==========

==========Social Media==========

==========Credits==========
🎨 Channel Art:
Profile Picture:

🎵 Ending music
Track: Debris & Jonth - Game Time [NCS Release]
Music provided by NoCopyrightSounds.

#Hyprland #Linux #Wlroots #Wayland #OpenSource #FOSS

DISCLOSURE: Wherever possible I use referral links, which means if you click one of the links in this video or description and make a purchase I may receive a small commission or other compensation.

[sunderkeenin]

aquamarine can't really be a giant waste of effort when:
1) the bundled wlroots is extra effort to maintain even compared to just having something Vaxry is specifically familiar with and is specifically made *for Hyprland's functionality*.
2) vaxry being banned from FDO means he can't contribute to wlroots and get wlroots to have a direction aligned with the future of Hyprland

There's both a technical maintenance/functionality reason to have Aquamarine and a practical/political reason to have Aquamarine.

[vaxryy]

unsure about the "giant wasted effort", wlroots does NOT have explicit sync yet (the release notes are a bit misleading, the backend stuff is not done yet) while we already do have explicit sync (sure, not 100% complete, but 95% of cases) thanks to the merge. HDR will likely come sooner too.

Also, aquamarine and the protocol implementations are NOT a "port" of wlroots. They ARE written from scratch. I've only taken inspiration and learnt by reading sources of wlroots/kwin. I've also had to rewrite wayland-scanner to generate C++ headers for wayland protocols instead of the C ones. There are some similarities in the architecture (like there will be in every wayland compositor tbh), but they aren't the same at all.

It's basically a new ecosystem, pretty much.

Also, at least for the next 2 years I don't predict anything will change with my contributions. After that, no clue. Really depends and life is very unpredictable.

Thanks for the coverage as usual! :)

PS: no plans for a generic wayland compositor library atm, I don't see a point of one and it wouldn't help with the direction I am bringing Hyprland in at all.

[tato-chip]

I just respect the man for essentially doubling his workload.

[JEM_Tank]

You make such a good point, SOO MUCH documentation doesn't have the explanation where the info going into the functions are coming from or examples for the inputs.
It drives me nuts!

[monkev]

I would argue that until wlroots is willing to commit to a 1.0, distros will need multiple package versions or vendor.

[SeralyneYT]

I wouldn't be surprised if Aquamarine is a Oshi no Ko reference.

[samuellourenco]

To me, it makes sense to port a project from C to C++, as the benefits can't be overlooked. If done properly, it will lead to cleaner, more compact and more readable code. Personally, I've ported some projects of mine from C to C++, a decision that I don't regret.

As for the lack of documentation, I can understand the reasons. Programmerss are not necessarily documenters.

[rodrigo.]

I mean speak anything about the man but he indeed do write documentation and this would be beneficial to future wayland compositors projects

[bittenup]

honestly at 8:10 usually it's because developers like to use the .h file extension

[liquidsnake]

Since freedesktop banned Vaxry i see this as a necessity, you cannot rely on a dependency you're not allowed to contribute to

[kuhluhOG]

wlr_output_send_present
Send a present event.

A yes, the type of documentation where you pretty much just repeat the function name, a subset of the useless types of documentation.

[segment]

I like writing documentation in the code. It helps me keep focused on what the function is supposed to do but, in the end I was fired because documentation do not provide any new code.

[aniketbisht]

Let's go C++ gang. Now I want a Wayland client library to be available in C++ itself, with convenient C++ API. That would allow C++ developers to have an option besides the bloated SDL (I like it btw) if you want to support only (or test on) Wayland platforms.

[Diego]

Well, Hyprland made me do 2 things I've avoided doing for years at all cost.. 1. Start using Wayland. 2. Distro hop to a distro that has better Hyprland support (imo) which is NixOS (btw). I wish the best for this project and every single person involved!!!

[SamiKankaristo]

C++ can be great or it can be terrible, it depends a lot on the programmer(s). If you write clean code, it's a great language; if you write bad code, it's easy to blame the language, because it won't stop you from doing that (unlike some other languages, which only have the one "correct" way of doing things). But that doesn't make the language bad (in my opinion), it just means that some of the C++ code out there is terrible.

You can write C++ that's basically like C, or you can use the fanciest templates, operator overrides, etc. You can write code that only uses things in the original C++ standard, or you can use the latest C++20 standard. Learning the basics of C++ is pretty easy, but you can also spend decades writing it and still learn new things (partly because new features are added with every new standard).

[dexterman]

Wow, this fella is such a technical genius.

[stam_ehad]

If only someone in the FDO did not ban him for dubious reasons, we would not be here

[jinliu]

The compositors of GNOME and KDE don't use wlroots. And for KDE (kwin) there are like only two maintainers. So it's quite normal and feasible for a Wayland compositor to implement the protocol on its own.

[drobotk]

Can't wait for the dev to ditch the linux kernel and make his own hyprkernel ;)

[vaayuo]

Nothing new here, just vaxry being a God tier developer.
I'm excited to see where hyprland goes, hope it doesn't die out anytime soon