Perl was included in the base system only up to version 4.x.
www.freebsd.org
perl fell out of favor around that time because of worries about where the perl language was headed in the future. Before the whole perl 6/Raku disaster it could be depended upon to be on just about any UNIX-like OS running on servers and desktops. Hence why it was so widely used during the early days of the web and why so many people opted to write scripts in perl instead of shell scripts. Since perl was
much easier to make truly portable. Although using perl did come with its own set of problems (mainly: Where is perl installed on this system vs. these other systems running a different OS?).
Anyway, the perl guys shot themselves in the foot after perl 5. People got terrified that their old stuff would no longer work on future versions. It took them years to finally decide what they were attempting with perl 6 was a horrible idea so they renamed the new version Raku. But by then it was too late and a lot of people had opted for Python instead. Which was gaining popularity at the same time popularity of perl was declining. perl went from
the standard scripting language everyone suggested a newbie to programming learn to something considered old hat. Hence why PHP took over the web quickly and why Python took over general purpose scripting for most everything else. In truth, we would have probably been much better off if everyone just stuck to perl. But complex one-liners are scary I guess and as we've seen over the past 25 odd years any pretense that good practice was going to be followed by the industry went out of the window. So now you get mountains of incompatible python, javascript, PHP and other "frameworks"/libs all wanting to pull in GBs upon GBs of stuff just to do basic things like generate an HTML document and fetch updates for parts of the DOM in the background. Hell we now have pseudo-websites pretending to be full blown system applications that want to pull in an entire browser engine for each and every application. Then the same companies/people pushing this "portable" soup of garbage claim we can make it secure if we just stuff it into yet another glorified chroot. The madness has even taken over systems programming now with new C-like languages wanting to have their own package managers that pull in ungoldy amounts of random source code at compile time (and sometimes runtime).
At least when we were all using perl the syntax was similar enough that it was a step towards understanding C. Now I have no idea how any children are expected to understand C code. Much less what C code compiles down to. To the new generation of programmers the OS might as well be a black box. Just like in my generation the CPU was already a "black box" that you weren't supposed to understand because assembly was "too hard" compared to the generation before mine that got to cut their teeth on stuff like m68k asm.
There is no real reason to write yet another rant about the situation with PID1 on Linux. They won't listen anyway. The average user of Linux these days is not the sharpest spoon in the shed to say the least. If you dare to not follow their dogma they prefer to come up with reasons to ban you from the discussion since they can't argue on technical merits. They hold all the moderator positions at places where discussion happens so there is no point in attempting to save them or their new version of Windows. If you want a good laugh check out what's happened on the LKML lately (I suggest starting with Linus's latest commits).
As I keep saying: I welcome something akin to s6 in the base system. But I don't have much faith in anyone attempting to re-invent the wheel yet again when a good service manager and a suite of tools built around it already exists. Whatever standards are set for scripting services will eventually be the only option. Since that's the only way things can be. Once it spreads into base it will eventually take over ports. As we've seen in the Linux world all alt-init/service mangers were quickly excluded from most distros because no one is continuing to provide shell scripts for package. Hence why something like s6 is not used very widely. To use it you must be competant enough to write you own scripts in execline for each and every daemon/package you want to use on your system. Maybe if you're lucky there will be an overlay (Gentoo) where someone else has done part of that work. But most likely whomever is maintaining that overlay isn't interested in everything you're interested in. So instead you mostly get systemd unit files and shims. Hence why Linux is a bit of a lost cause now. IBM's plan to own userspace has worked so now even the "non-systemd" distros are just running 80+% of systemd stuff via shims and giving you a different PID1. I suppose this is better than running a complex PID1 consisting of about 1 million lines of code with complex code paths. At least something like runit or s6 is small enough that one person can understand it and you don't have to worry about it crashing randomly taking the entire system down with kernel panic or some "unintentional" bug exposing a back door into every server and desktop/laptop out there running mainstream Linux (totally a conspriacy theory I'm sure

).
Well, I must have missed when that happened. ;-) I have Perl installed on all my machines. Anyway, Shell is pretty much eloquent for this purpose.
Friend I'm not sure why you didn't read what I linked above that explains in great detail why shell scripts are horrible for this purpose. Yes we made do with them for many decades. No they were never a good idea or suited for this type of thing.
The main issue with shell scripts
is parsing and then second is portability. Even if you write to POSIX standards shell scripts are never going to be truly portable. That's how it has always been and that's how it always will be. Shell scripts are also horribly insecure and the performance is terrible. Again see:
https://skarnet.org/software/execline/dieshdiedie.html
Perhaps you don't like Lua but again out of all the programming languages in common use that could have been selected it's most likely the best choice. It's small, it's written in ANSI C and finally it's widely already used as a scripting language in many other applications. This makes it a great canidate to be included in the base system. Finally, it's very unlikely it will change much in the future or suffer the problems that have plauged other scripting languages like perl and python (among many others). Learning Lua is worth your time and you will find as much value out of knowing it as you do knowing how to write shell scripts. If you
really insist on sticking to shell scripts for firing up daemons then you can still do it via Lua. Which is most likely how most things will be supported (just like s6 and execline) until all scripts in base are re-written directly in Lua. After that it won't be long until most ports follow. At which point you'll be on your own if you inisit on continuing to use shell scripts for these purposes. The new service manager's way of doing things will become the default. It always happens.
This will be a positive change as long as rcd ends up being good and doesn't go down the path of so many badly written init/service manager schemes from the past. Only time will tell.
Bit of a Rant follows:
There are actually much more concerning things happening in userspace to worry about. The fact of the matter is very soon FreeBSD (and all the other BSDs) are going to be put in a position where they'll either have to start maintaining a lot of software themselves that they've been pulling from "upstream" (read: IBM/Linux) or they'll be forced to adapt to using what "upstream" is shitting out as of late. This means things like having to drop support for X11 in favor of wayland or having to emulate stuff like logind (or write shims/wrappers around Linux's versions of these tools). Thankfully, on the X11 front the OpenBSD guys will probably be maintaining Xenocara for a long time to come. So we're okay there unless FreeBSD's developers decide to go all-in on Wayland and suffer from the same problems that are happening with mainstream Linux. But if we don't go all-in on Wayland we're going to be in a position soon where we'll be forced to start maintaining stuff like GTK, Qt, KDE and Gnome on our own. I personally think we should just stop putting in the effort to port things like GTK, KDE and Gnome while going back to maintaining gtk2 (maybe gtk3) and Qt 5/6. There is good effort happening on the gtk2 front lately. It seems more people are waking up to the madness that is Gnome/gtk4 and finally some people are getting behind keeping stuff like gtk2 going and adding new features to it. Thankfully, most things written around gtk still compile just fine with gtk2. Same is true of most stuff written for Qt.
I would personally enjoy seeing more effort going behind
Arcan and its A12 protocol. Which most people don't seem to even know exists. Despite the fact that it already supports all X11 and Wayland applications out of the box and brings many new exciting features to the table. Like true support for networked GUI applications. I have Arcan running on a bunch of desktop systems on my LAN and it can do amazing things. For example, I can fire up a Neo-Geo emulator, load a ROM in it then drag+drop the window to any other machine on the LAN. It sends state over the wire
fast and everything just works. I can even transfer the full state over to another machines CPU/GPU/IO/Input devices or I can continue running it on the machine where I first launched it and only send over video/audio/input events. It just works either way. It's really exciting software that solves a lot of problems people claim are either impossible or too hard to solve. The guy has been quietly working on Arcan for years with a small group of developers yet you'll never hear a peep about it on the major discussion platforms where the Linux people are constantly arguing over X11 vs. Wayland with the same tired arguments and talking points we've seen mulled over for 18 years now.
I would really like to see a major shake up in the FreeBSD base system where a lot of stuff currently installed by default was
kicked out and users told they have 1-2 years to prepare for it. There is a lot of cruft in the base system that only exists for old systems running old configurations. It's why FreeBSD requires so much configuration up front to get it going correctly on most systems. It's why a lot of the current defaults are not secure. Much of this stuff should be kicked out to ports and things like the firewall should be cut down to one default option (I vote for pf) and anyone with a "legacy" system that wants something different should spend the time to get their configuration going with the port instead of expecting that stuff to continue to live in base. But I know this is not going to happen any time soon.
Believe it or not in many ways OpenBSD is better for most users on the desktop (and even laptops) because they keep their base system small, they offer a secure X11 implementation at install time that just works at first boot and they don't have problems like 3 different firewalls in their base system. Sure you won't get things like 32-bit support or wine (well wine is in their ports tree now as of a couple of weeks ago) but you will get a well documented coherant system with good base system that's well tested. Since most developers of OpenBSD are actually using it as their day-to-day desktop. Unlike Net/FreeBSD where most developers seem to be using it as a secondary system where they use something else for their desktop OS (I see a lot of Apple laptops at conventions, just sayin').
All that aside in FreeBSD we're already relying on a lot of things we shouldn't be. The Nvidia drivers make us beholden to Nvidia to provide binary blobs. The entire graphics stack/DRM is ported from Linux's kernel now (same is true of OpenBSD as well). A lot of wireless chipsets are badly supported by native drivers or require using the Linux drivers through a wrapper. I could go on but you get the idea. A lot of crucial things in kernel/base depend heavily on an "upstream" beyond our control that's quickly diverging from the BSDs and the developers of such things are pretty open about the fact that they don't care about supporting anything but what IBM pays them to support (which means the Linux kernel in the vast majority of cases).
Another big issue is even the Linux kernel is quickly dropping support for "legacy" hardware. By "legacy" they mean pretty much everything made before 2010. In a year or two running the Linux kernel on a lot of systems currently using it is going to become impossible due to their latest round of removing a lot of drivers due to hypothetical exploits found using LLM tools which weren't even tested (or attempted to be fixed assuming they are actually exploitable) before getting removed). So an influx of people looking for a different UNIX OS for "legacy" hardware is likely coming in the next few years. If FreeBSD decides to follow suit this will leave a lot of folks with no viable OS for those systems. Aside from maybe OpenBSD and NetBSD. With the latter while a nice community they often go years without testing their automated builds are actually working on systems they claim to support. As anyone that's tried to install NetBSD on a Dreamcast or comparable system has found out first hand.
My greater point here is there are much bigger issues than worrying about if something like a new service manager is base is going to turn into systemd in all but name.
Someone like me will be okay in the future because 1) I'm willing to accept running something like OpenBSD and doing without some things I get in Linux/FreeBSD and 2) I'm okay building things from source, setting compile time options and running "legacy" software even on a system with network access. Since I actually have a dedicated firewall and most of the hypothetical exploits don't scare me/don't affect me. But I do worry about what's going to happen to the vast majority of users that aren't willing to do these things (or learn how to do these things). I'm also worried about the fact that it's becoming
very hard to find people that can even understand how something like the BSD/Linux kernels work. Many new programmers can't read C or refuse to learn C.
Many younger people don't even grasp the concept of how the FHS work. It has really gotten bad. I've been working with some recent graduates this past week that claim to be good programmers but they can't even do something as basic as write a web page in HTML directly or know how the man command works. I'm serious. But they'll argue for hours among themselves online about how something like Rust is better than writing things in C and tell you to "get with the times". Most of them can't even write those rants themselves they just prompt and LLM to do it for them and they're totally lost without a connection to the internet. I assigned some basic tasks to one of them on a machine without network access a few weeks ago. We do not allow cell phones in that room (and they can't talk to the cell network in there anyway). I gave them somthing incredibly basic that any child of the 1980s/1990s should have been able to do on their own. They had full access to the man pages and there were multiple books on the shelf they could have read that would have walked them through the task I assigned. When I came back to check on them a few hours later they hadn't done anything and blamed their lack of work on not having access to google. They obviously didn't last the week and I'm not sure how they even got to me in the first place. This person had a degree, multiple certs. and somehow managed to pass all the tests before they got hired. They are not the first one I've had be totally useless. I don't mind training on the job (in fact, I prefer it) but I can't train someone that can't even navigate the file system or read man pages. I don't have time for that. They knew less than my Grandmother and I still have to maintain my Grandmother's desktop PC and all her other crap (Ring cameras, cell phone, tablets etc.).
The users are getting dumber but our programmers are getting
much dumber in my expereince. At least those calling themselves terms like programmer/coder. This isn't unique to CS I'm seeing the same problem happening across all fields I interact with on a weekly basis. The worst thing that ever happened to CS (and the internet as a whole) was "geek chic" becoming a thing. People want to appear like they're into technology now instead of like the good old days when they used to laugh at the geeks in the computer lab. They want to make the $120k+ a year salary they heard about. But they don't want to put in the butt time to actually learn how to do this stuff as my grumpy old professor used to call it. Worse yet, I'd argue many coming into the field never had the ability to learn this stuff in the first place. But a lot of them were pushed along ("no child left behind") to fill quotas and/or to prevent making the insituations they attended look bad. I know a lot of them straight up cheated their entire way through. Which is why we don't hire graduates coming from a handful of universities anymore (mostly from overseas) since it's obvious to everyone those "accredited institutions" are simply diploma mills.
I'll even go futher and say this: The people you actually want in this field are smart enough to see the writing on the wall and know it's a bad investment in their future to join the field in the 2020s. We're probably living through the last years of real CS now. At least for the vast majority of people. Most tasks will be fully automated soon and only a very select number of people will actually understand the software running the world or be given access to those systems. The rest of us are going to get dumb terminals and we're going to rent time on the real system living in a datacenter someplace. The era of commodity hardware is coming to an end. I hope you saved all your old hardware while you still could. Soon things like consumer GPUs for playing video games locally are no longer going to be produced for the average consumer. You won't be able to buy the ones going into the datacenters either because the hardware will be considered a state secret and access to it will be extremely limited. As it stands they're already black boxes at this point anyway. They did an end-run around x86 being a relatively open platform by pushing stuff over to the blackbox GPU. IBM and friends aren't going to make the same mistake they made with x86 twice.