Forgot your password?
typodupeerror
GNU is Not Unix Open Source Programming Linux

Paid Developers Power the Linux Kernel 191

Posted by timothy
from the back-in-your-day-maybe dept.
Hugh Pickens writes "Believe it or not, there is still this illusion that Linux and open-source software is written by counter-culture, C++ programming cultists living in their parents' basements or huddled together in Cambridge, Mass. group-houses. Now CNet reports that the Linux Foundation has found that 'over 70% of all [Linux] kernel development is demonstrably done by developers who are being paid for their work.' That Linux is primarily developed by paid developers should come as no surprise considering that Linux enables many companies — hardware, software, and online services — to be more competitive in their markets and to find new ways to generate revenue. 'What's important about how Linux and open-source software is created isn't the side issues of politics or how its developers are perceived; it's that its fundamental methodology produces better software,' writes Stephen Vaughan-Nichols."
This discussion has been archived. No new comments can be posted.

Paid Developers Power the Linux Kernel

Comments Filter:
  • by razvan784 (1389375) on Sunday December 05, 2010 @09:23AM (#34450088)
    It's written in C, not C++.
  • What? (Score:2, Informative)

    by QuaveringGrape (1573239) on Sunday December 05, 2010 @09:30AM (#34450114)
    The Linux kernel is written in C, not C++. And haven't there been a number of articles on how IBM, RedHat, Sun etc all have employees who develop Linux? One post in particular... [slashdot.org] and I know there have been others.
  • Old News (Score:5, Informative)

    by PiAndWhippedCream (1566727) on Sunday December 05, 2010 @09:36AM (#34450138)
    Do even the editors read [slashdot.org] anymore?
  • by petes_PoV (912422) on Sunday December 05, 2010 @10:18AM (#34450346)
    I doubt this has been the case for 10,15 years or more. The fact is that most of these "counter culture" people are inventions of the media or hollywood and have never, really, existed in the real world. The few people who would describe themselves as such may still exist in some parts of the world, and are usually referred to as criminal hacking gangs, but they've not contributed a dam' thing to the Linux kernel.

    That's not to say some individuals with long hair and others with low personal hygiene standards haven't done their bit, but those attributes don't make you counter-culture.

  • by Attila Dimedici (1036002) on Sunday December 05, 2010 @10:43AM (#34450470)
    If they aren't interested in that, how do you explain all of the companies that pay programmers to work on Open Source?
    Most (if not all) of those companies already had programmers on staff to write custom software for the company. They discovered that it was easier and cheaper (and often better) to modify Open Source Software than it was to write their own application from scratch (or to buy such an application from some proprietary vendor).
  • by Tacvek (948259) on Sunday December 05, 2010 @11:06AM (#34450572) Journal

    Because Bjarne Stroustrup's C with Classes language is merely an early version of C++. I mean modern C has evolved quite a bit since that time, and it would be a shame to have to limit yourself to the C language constructs of 1983.

  • by cduffy (652) <charles+slashdot@dyfis.net> on Sunday December 05, 2010 @11:23AM (#34450692)

    I don't see how money is being made with "several companies bankrolling" a piece of software that scratches a common itch. Is it that a particular company sees that it can make money by using, though not owning, a particular piece of software and they don't mind their money making improvements available to other people?

    Typically it's "bankrolling" by assigning some of your people to spend some of their time on making improvements you happen to need and contributing them upstream.

    (Contributing improvements upstream means that you won't need to continually maintain your patches, that they'll eventually be included in vendor packages/kernels and thus that you'll later need to do less packaging yourself, and is otherwise a money-saving action. As a somewhat-related aside -- once upon a time I worked in embedded Linux, and you had companies who structured their default contracts for kernel work such that everything was submitted upstream, making each contract effectively a one-time engagement when everything was done right, and others who didn't... ehh... encourage their clients to pursue submitting their code, such that said clients would keep paying in to keep their patch current with newer upstream kernels).

A sheet of paper is an ink-lined plane. -- Willard Espy, "An Almanac of Words at Play"

Working...