Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
×
Open Source Programming Linux

Linux Kernel Developers and Commits Dropped in 2019 (phoronix.com) 37

Phoronix reports that on New Year's Day, the Linux kernel's Git source tree showed 27,852,148 lines of code, divided among 66,492 files (including docs, Kconfig files, user-space utilities in-tree, etc).

Over its lifetime there's been 887,925 commits, and around 21,074 different authors: During 2019, the Linux kernel saw 74,754 commits, which is actually the lowest point since 2013. The 74k commits is compares to 80k commits seen in both 2017 and 2018, 77k commits in 2016, and 75k commits in both 2014 and 2015. Besides the commit count being lower, the author count for the year is also lower. 2019 saw around 4,189 different authors to the Linux kernel, which is lower than the 4,362 in 2018 and 4,402 in 2017.

While the commit count is lower for the year, on a line count it's about average with 3,386,347 lines of new code added and 1,696,620 lines removed...

Intel and Red Hat have remained the top companies contributing to the upstream Linux kernel.

This discussion has been archived. No new comments can be posted.

Linux Kernel Developers and Commits Dropped in 2019

Comments Filter:
  • Then why the hell Intel processors have so shitty power management in linux?
    • Re:Intel?? (Score:4, Interesting)

      by Kjella ( 173770 ) on Saturday January 04, 2020 @08:32PM (#59587410) Homepage

      Because the Linux money is in the server/workstation/cloud market, where sleep states and battery life means very little. According to StatCounter the Linux desktop web market share was 1.85% and on Steam it's 0.67%. There's of course Android too but it runs on ARM, so nobody really works to optimize Linux for x86 laptops except maybe a few from Google making Chromebooks.

      • Re:Intel?? (Score:4, Informative)

        by That Ordinary Guy ( 6159720 ) on Saturday January 04, 2020 @08:53PM (#59587454)

        Good point! Also, Linux often use generic power management features defined by some kind of standard. Of course, Linux open source code has some specific tweaks to handle specific vendor hardware but in the end, it is lacking a lot of functionalities implemented by vendor binary blobs available under Windows and Apple. Some vendors provide Linux binary blobs for their hardware and I have used them quite a few times (your kernel becomes tainted). A very few provide their full up to date API in order to handle the hardware.

        In the end, it is similar to installing and booting a new OS and using "generic vga" in order for the screen to work until you install more performant drivers. With Linux, sometimes your only choice is to use "generic whatever". Even when there are some optimizations available for Linux, they often trail behind.

    • Re:Intel?? (Score:5, Funny)

      by Aighearach ( 97333 ) on Saturday January 04, 2020 @09:53PM (#59587626)

      The few of us with linux laptops usually just choose the model with the Beluga whale battery pack sticking out the bottom, and then rarely use it off power.

    • Power management doesn't quite work on any laptop I've ever used. I use it but it's never perfect. Even my Macbook Pro would do things like losing USB ports, and ultimately just locking up, if not rebooted through too many suspend/resume cycles. It's like how we can't cure the common cold.
    • by xiox ( 66483 )

      I think that is outdated, at least for some brands. I have a Thinkpad Carbon X1 and a Dell Inspiron - both get very good battery lifetimes in Linux (8-12hr). A lot of this comes down to the BIOS and firmware.

  • Re: (Score:1, Interesting)

    Comment removed based on user account deletion
    • by rtb61 ( 674572 ) on Saturday January 04, 2020 @08:35PM (#59587422) Homepage

      Too late, big developments in Russia, China and India. So probably yeah, you would see a whole lot less coming out of Russia, China and India as they will inevitably host their own forks, no longer trusting the USA for anything what so ever. So contributions from those sources will drop, then there is the EU, how far off is an EU hosted Linux because they also no longer trust the USA. USA hosted tech is likely to suffer in this environment, especially FOSS as the US kernel will mostly only end up with US contributions and will have to seek out the others.

      There will be much forking and we can all guess exactly who will end up dominating FOSS in order to globally crush US tech firms, China (the Huawei ban was the single stupidest possible thing the US government could have done, ramifications across the whole planet, US tech can no longer trusted not one little bit, the cost to M$ huge).

  • by fleeped ( 1945926 ) on Saturday January 04, 2020 @08:50PM (#59587448)
    They should always only go up. Yes, that sounds sustainable.
  • A CoC will (Score:1, Troll)

    by AHuxley ( 892839 )
    do that.
    Return to code productivity.
    Work on a CoC does not add the computer code needed for the productive parts of a OS.
  • More stuff is going into systemd so there's less need for code in the kernel. /s

  • by BAReFO0t ( 6240524 ) on Sunday January 05, 2020 @06:26AM (#59588390)

    Our capitalist views may be skewed, but in nature, there are only two types of processes: A) Exponentially growing ones, and B) *surviving ones*.

    Because anyone with a leftover bit of common sense, quickly realizes that in a world with finite resources, the former means resources will run out, or waste will drown it, and the process will die.
    Unless some "friction" counter-force starts to emerge, to balance it out, and make it *stable*.
    Except, of course, when some moron (*looks at TFA*) comes along, and yammers "Oh noes! Teh stagnation! It is death! Do away with teh friction!" until the balance derails and we're right on track towards death again. ... Great job! A+! --.--

  • A long time ago I encountered an irritating issue in the Linux soft realtime scheduling. Some hours of bug hunting later, I submitted a 1 line patch that fixed the issue.
    Some years later, an issue in a netcard driver caused me some grief. I emailed the maintainer for that driver and he fixed the issue.

    These two small contributions were both fairly easy - in each case the code involved was small enough to understand with only a little time spent studying it, and the problem (and its solution) wasn't that obs

  • Comment removed (Score:4, Informative)

    by account_deleted ( 4530225 ) on Sunday January 05, 2020 @10:18AM (#59588704)
    Comment removed based on user account deletion

One man's constant is another man's variable. -- A.J. Perlis

Working...