Announcement

Collapse
No announcement yet.

Systemd Is Approaching 1.3 Million Lines While Poettering Lost Top Contributor Spot For 2019

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Systemd Is Approaching 1.3 Million Lines While Poettering Lost Top Contributor Spot For 2019

    Phoronix: Systemd Is Approaching 1.3 Million Lines While Poettering Lost Top Contributor Spot For 2019

    As of New Year's morning, systemd's Git tree was at 1,273,896 lines spread across 3,522 commits built up over 42,700+ commits from around 1,500 different authors...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    Are there any former active contributors that stopped systemd activities in 2019?

    Comment


    • #3
      Originally posted by patrakov View Post
      Are there any former active contributors that stopped systemd activities in 2019?
      Read the article. "There were about 305 developers active on systemd in 2019, down from 353 the prior year."
      So yes, there were obviously some contributors in 2018 that didn't contribute in 2019. I'm guessing the reason is that they weren't major contributors, rather than anyone objecting to the direction of the project and rage quitting.

      Comment


      • #4
        Devuan got it all wrong. Systemd is not the main problem. The real culprit is Linux.
        Linux kernel violates all UNIX principles (besides, it's not even UNIX).
        It is a single monolithic repository with 27.8 million lines of code that can not be taken apart.
        The Linux kernel is forcefully pushed to us by multi-billion dollar corporations like Redhat and the likes.
        Devuan should dump this malicious attempt of corporate infiltration into OSS ecosystem and switch to Gnu Hurd instead.

        Comment


        • #5
          Originally posted by pkese View Post
          Devuan got it all wrong. Systemd is not the main problem. The real culprit is Linux.
          Linux kernel violates all UNIX principles (besides, it's not even UNIX).
          It is a single monolithic repository with 27.8 million lines of code that can not be taken apart.
          The Linux kernel is forcefully pushed to us by multi-billion dollar corporations like Redhat and the likes.
          Devuan should dump this malicious attempt of corporate infiltration into OSS ecosystem and switch to Gnu Hurd instead.
          GNU Coreutils is ~200K lines and gnulib is ~1.1m

          You're going to need to get rid of those too.

          Comment


          • #6
            Originally posted by pkese View Post
            Devuan got it all wrong. Systemd is not the main problem. The real culprit is Linux.
            Linux kernel violates all UNIX principles (besides, it's not even UNIX).
            Sorry you are being very narrow minded. There is not a single kernel in any Unix or Unix like OS that does not violate most if not all of the UNIX principles.

            The real culprit is kind of larger than Linux. Linux was started to be a cheap option to commercial Unixs thinking they are screwed at designed level you kind have to expect Linux to be stuffed up as well.

            Originally posted by pkese View Post
            It is a single monolithic repository with 27.8 million lines of code that can not be taken apart.
            The first Unix/BSD kernels areMonolithic right down to being monolithic with drivers and being unable to be taken apart and work. Linux kernel as single huge monolithic repository is just a continuation of way early Unix world did things.

            Unix principles and the way Unix/BSD were implemented don't in fact align at all. Fact Linux is based off Posix and other documents like that formally wrote down how the Unix/BSB implementations were done not the Unix principles leads to something that is not very close to Unix principles because the source material was not very close to Unix principles.

            Originally posted by pkese View Post
            switch to Gnu Hurd instead.
            Sorry to say Hurd violates a key UNIX principles biggest being the following.


            You are after operating systems that obey UNIX principles correctly you are looking for operating systems like plan 9(yes this comes from the guys who wrote the Unix principles and wrote the early Unix kernels that they admit they stuffed up) or redox. These do obey everything is a file including process identifiers.

            Linux kernel now is starting to move away from its Unix implementation clone/posix roots and starting to move more in the direction of obeying more proper UNIX principles. Changing stuff without breaking legacy applications may be insanely hard.

            Comment


            • #7
              yes, we should split any project over 2000 lines of code into something smaller.

              Comment


              • #8
                All the various quotes replying to pkese
                Congrats, you've all been successfully trolled. Don't you feel silly?

                Comment


                • #9
                  I would like Systemd to clean/close its more than thousand opened issues. That would be a great indicator.

                  Comment


                  • #10
                    It just needs only one to continue to exist.

                    Comment

                    Working...
                    X