what he mean is that /etc/rc.local isn't not used again in debian. the file is still there but it only contain 'exit 0' as default. the script was moved to somewhere (I forgot which one) but user still could use rc.local if they want (like I did). since I'm not using systemd-sysv /etc/systemd/system/rc-local.service isn't exist. it seems to me that rc.local is executed not directly by systemd. debian might still using sysvinit to executed them just like another services.

kurotsugi@kurozv3:~$ cat /etc/rc.local
#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.
#brightness setting
chmod 777 /sys/class/backlight/acpi_video0/brightness
echo 5 > /sys/class/backlight/acpi_video0/brightness
exit 0

I have brightness setting script due to a bug in my laptop but I think it should be safe to delete all that line.

well...it's not the boot time. manjaro have nice xfce desktop and they have a lot of cool tools for user. the things that prevent me from using them is my unfamiliarity with pacman and downloading the iso. I live in indonesia and with my slow internet connection it might take a whole day to download the iso

I think the real power of systemd is only seen after properly enabling the parallel loading of startup services. By properly, I mean setting up systemd to do parallel loading and prioritizing loading of services intelligently to achieve the desired effect. Merely installing systemd with its default configuration won't do much.

every systemd release tends to tremendously huge and introduce lots of new bugs. it's normal for a distro with 'stability' in their mind to pick the matured, bugless, older version. even a bleeding edge distro like arch haven't use the latest version yet. manjaro is still on 212.