With Manjaro architect we have systemd-support at installation time. right after that the user needs to create loader files for systemd-boot for every new release by themself.
Since systemd-boot is so much slimmer and easier to manage, compared to grub, on UEFI setups. I think we should have it supported by our kernels.

I was trying to make a alpmhook / script for it but I’m stuck at 2 points.

get the UUID of the root partition. Since I don’t want to utilize the fstab (since I dont know if there is even a fstab, or if it has a UUID in it, I cant use it at all)

deal with the “is it a systemd-boot or a grub setup”-issue.

I also don’t want to enforce it, since this whole thing is a EFI only solution. But would you like to have this feature in Manjaro?

To expound, “bootctl install” is to create a efibootentry and a efi-file “/EFI/systemd/systemd-bootx64.efi”. We will still need to create entries.

Personally, I agree systemd-boot is quite simple though refind can automatically detect efi-files at boot and present the boot entries for them. We just have to manually create entries for systemd-boot. And systemd-boot is fast, very fast. refind is pretty though.

That said, I still think grub is simplest (yet powerful and automatic). The complexity that people find - and I understand what they are saying - is due to ‘clever’ OS developers trying to use the capabilities of grub’s facilities to further extend grub’s reach into areas that are not necessary; by the use of extraneous /etc/grub.d/ (like 01_menu_auto_hide) and grubenv variables (like boot_indeterminate and boot_success). Oh, and we can make grub very pretty too, and in much more many forms.

To reiterate, that is my personal opinion and I have no interest to influence what people choose for the bootloader. Just glad we in linux are spoilt for choice. (I choose to use grub, just not Manjaro’s)
[Except for cheesecake - “There is no alternative!” - to quote Margaret Thatcher]

loader files for kernel and fallback (sitting in /boot/loader/entries/*.conf

We only need to generate new loader files for new installed kernel, new installed and UCodes. We also need to remove them on kernel/UCode uninstallation.
So there is also no need to re-generate them after a mkinitcpio.

Btw Solus has systemd-boot, and as far as I remember by default $esp’s mount point is /boot/efi there. Also they make use of clr-boot-manager or how it’s called I don’t remember. I mean, no need to invent the bicycle if it’s already implemented somewhere.
Below are some thoughts of mine, feel free to disagree:
Using /boot as $esp just because of one more bootloader (in fact not the most feature-rich or unique) is somewhat not thoroughly thought of, and may cause a mess, especially in people’s heads. There are really few people who like to tinker with their bootloaders, and for the absolute majority such things should be just as reliable as possible with no need for manual intervention (even Grub gets broken from time to time according to the forum’s posts).
I had no intention to offend anyone, sorry for being rude, the above are just my thoughts regarding so-called bootloader.

Using /boot to mount $ESP is what architect sets up. I dont want to deal with that or change already installed systems, since it works fine. Also I dont have plans or any need to convert people from grub to Systemd-boot (SDB). Grub people will still get /boot/efi and thats just fine how it is. This is entirely only for the SDB path of installations (or for people who want to switch over).

openminded:

in fact not the most feature-rich or unique

Thats why I like SDB. It’s just a simple loader, nothing more, no special setting or beautiful backgrounds to create, no rebuilds, no nothing. You set it up one time and it will work until you want to try a new kernel.

openminded:

such things should be just as reliable as possible with no need for manual intervention

Thats the excapt point why I use SDB for me and my family, instead of GRUB. I’m sick of having errors, missing filesystem support, a broken boot because of some config changes or fighting of multiple linux grub implementations. But that is not the topic in here. Again - I dont want to replace Grub in Manjaro. I only want to have actual support for it in manjaro, because you can install manjaro right now with support for it.

openminded:

Copying kernels and initrds to fat32 partition is another example of “ingenious thinking”, IMHO.