There is a question that is very similar, which is – “Why do schools require uniforms?”My son’s high school is an arts school, where most students study performing arts, broadcasting, fine arts, and other artistic majors. One advantage of such a school is that the average attractiveness of students is higher compared to regular high schools! Every time I pick up my son after school, I see those fair-skinned girls radiating youthful energy in the sunlight, and I really miss my high school days! Okay, I digress a bit! In this school, there is a rule – “No alterations to the uniform design are allowed!” This rule must have been concluded by the teachers through experience. After all, beauty lies in the details; today the waistline is raised, and the legs are shortened a bit. Students must have done this in the past, which caught the teachers’ attention. If students focus all their energy on their uniforms, it would definitely lead to endless comparisons, each with their own little thoughts. The main point is that during the student phase, what matters is the grades. A uniform uniform allows everyone to focus on improving their grades rather than on what you wore today or what I should wear tomorrow! In the long run, uniformity in school uniforms is a very good strategy; it prevents comparisons and promotes unity, and any changes are easily noticeable! This is the power of uniformity. From this perspective, I strongly support Systemd! From a user’s standpoint, once you learn SystemD, you can utilize that knowledge to start/stop services, check service status, define startup items, view logs, and check startup dependencies. Isn’t that great? Just do one thing well. If it were still like before, where one distribution is configured this way and another that way, it would actually be less user-friendly and not conducive to operation. If we were to return to the era of init.d, we would still need folders to write scripts, isn’t that cumbersome? Therefore, I personally believe that a unified Systemd is a good thing, at least in such a “divided” Linux community, it is a good thing. It allows everyone to realize that if we come together, we can accomplish something, and as long as everyone supports and agrees, we can improve together and make it as convenient and quick as commercial operating systems (like certain Windows) ! As for the so-called “massive” issue, Systemd has only 600,000 lines of C code, which is not considered very large. Some people believe that “simplicity is best”; Keep it Simple has always been one of the system philosophies of Unix and Linux. Of course, for Ken Thompson (the creator of Unix), who said, “My wife went back to her family, and I was bored, so I wrote an operating system,” simplicity was a good choice at that time. This philosophy of simplicity is also one of the characteristics of its success. Not pursuing perfection but practicality is certainly good. However, reality is complex, and software is precisely meant to serve reality. Therefore, software must inevitably evolve towards complexity, which is the trend. In the process of evolution, the emergence of software that is more aligned with reality, more complex, and more “realistic” is an inevitable development direction. This is the reason for the inevitable emergence of Systemd. The development of Linux requires its existence. This is why Redhat and Debian have turned to Systemd. What do you think? I am Mingyue, an Internet Linuxer!