I'm on my second day of using Garuda KDE Dr460nized and I really how the team created a beautiful operating system based on Arch.
When I boot into GRUB, I find it MUCH better than Ubuntu's one (I would compare this to Manjaro's take on their boot selection) but since everything about this edition is supposed to look AMAZING then why not the bootloader?
rEFInd isn't the best looking bootloader in my opinion, BURG is. The problem is that BURG is old + deprecated, so it's not practical anymore.
Here is a picture of a BURG boot screen that I would love to see on a Garuda installation:
Summarization,
I would love it if for UEFI devices in the installation you could provide an option for a more user-friendly bootloader. This is not at all a priority since most of your time is spent in operating systems, not in the bootloader , but regardless it would be a nice addition.
We already have had a discussion over reEFInd as well as Burg and a lot of other bootloaders, but we had to reside with current one, especially due to timeshift.
LOL when I was writing this post I thought of how it would be implemented, and providing different ISOs was what came to mind first.
I was thinking that post-installation, the setup assistant would provide an option if you wanted to install a different bootloader depending on if you had UEFI enabled.
Garuda Suckless will use rEFInd in the live installation image, as it's much smaller then GRUB, and I will definitely make a page about configuring it in the manual, but until rEFInd or BURG or any other bootloader supports BTRFS snapshots, we will not switch to it.
Might seem a bit unnecessary and overkill, but perhaps the Garuda Linux team could code their own custom bootloader just for the distribution, one that provides this integration?
Or they could send a request to the rEFInd team to include this integration...