Slashdot Mirror


Linux Foundation Puts the Cost of Replacing Its Open Source Projects At $5 Billion

chicksdaddy writes: Everybody recognizes that open source software incredibly valuable, by providing a way to streamline the creation of new applications and services. But how valuable, exactly? The Linux Foundation has released a new research paper that tries to put a price tag on the value of the open source projects it comprises, and the price they've come up with is eye-popping: $5 billion. That's how much the Foundation believes it would cost for companies to have to rebuild or develop from scratch the software residing in its collaborative projects.

To arrive at that figure, the Foundation analyzed the code repositories of each one of its projects using the Constructive Cost Model (COCOMO) to estimate the total effort required to create these projects. With 115,013,302 total lines of source code, LF estimated the total amount of effort required to retrace the steps of collaborative development to be 41,192.25 person-years — or 1,356 developers 30 years to recreate the code base present in The Linux Foundation's current collaborative projects listed above.

146 comments

  1. Dr Evil! by Anonymous Coward · · Score: 0
    1. Re:Dr Evil! by tripleevenfall · · Score: 1

      Is this like that facebook meme where if you added up everything a mom does in a day, it would cost you ONE BEEEELION DOLLARS a year?

    2. Re:Dr Evil! by Anonymous Coward · · Score: 0

      Think you got it backwards. Where do you think such a thing on Facebook would have come from?

      With that in mind, are there any memes spawned by Facebook aside from sarcastic Likes or shows of pathetic retribution by unfriending?

    3. Re:Dr Evil! by invictusvoyd · · Score: 2

      Chick Norris can rewrite the entire kernel in a day . Without a single bug.

    4. Re: Dr Evil! by silentcoder · · Score: 1

      Is she Chuck's sister or his drag act ?

      --
      Unicode killed the ASCII-art *
  2. What is the cost of the QEMU code? by Joe_Dragon · · Score: 1

    What is the cost of the QEMU code?

    1. Re:What is the cost of the QEMU code? by Tough+Love · · Score: 1, Troll

      What about Linux kernel? Bearing in mind that several trillion dollars of industry now depend on it.

      --
      When all you have is a hammer, every problem starts to look like a thumb.
    2. Re:What is the cost of the QEMU code? by Anonymous Coward · · Score: 0

      Bearing in mind that several trillion dollars of industry now depend on it.

      Why bear that in mind? It has nothing to do with the replacement cost.

    3. Re:What is the cost of the QEMU code? by Tough+Love · · Score: 1, Troll

      Bearing in mind that several trillion dollars of industry now depend on it.

      Why bear that in mind? It has nothing to do with the replacement cost.

      Law of supply and demand.

      --
      When all you have is a hammer, every problem starts to look like a thumb.
    4. Re:What is the cost of the QEMU code? by Anonymous Coward · · Score: 0

      It costs nothing (actually it has a negative cost) to replace Linux with FreeBSD.

    5. Re:What is the cost of the QEMU code? by Hognoxious · · Score: 1

      They're very nice, but what do they have to do with the replacement cost?

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    6. Re:What is the cost of the QEMU code? by Anonymous Coward · · Score: 1

      Not quite. You have to add in the cost of writing all those drivers for devices which Linux supports but FreeBSD doesn't.

      On the other hand, getting rid of systemd is worth something.

    7. Re: What is the cost of the QEMU code? by Anonymous Coward · · Score: 1

      Getting rid of systemd, indeed. Where can I sign up?

    8. Re:What is the cost of the QEMU code? by 0dugo0 · · Score: 1

      Right, as if free/net/open- bsd self hosting without the help GNU tools.

    9. Re:What is the cost of the QEMU code? by Anonymous Coward · · Score: 1

      FreeBSD depended on the GNU tool chain (GCC, Binutils, GDB, etc.) to get where it is now, but will soon not make use of any of these.

    10. Re:What is the cost of the QEMU code? by Tough+Love · · Score: 1

      If there is no demand then there is no replacement, hence no replacement cost. If there is high demand then replacement cost will be higher because the price of replacement will go up. Law of supply and demand.

      --
      When all you have is a hammer, every problem starts to look like a thumb.
    11. Re:What is the cost of the QEMU code? by Anonymous Coward · · Score: 0

      Qemu is for cows.Cows say MOOOOOOOO.MOOOOOOOOO.MOOOOOOO.MOOOO says the cows.You Qemulated cows.

  3. erhm by Anonymous Coward · · Score: 0

    is that 5 billion american 5,000,000,000.0 or 5 billion, 5.000.000.000.000,0 the rest of the civilized world?

    ymmv

    1. Re:erhm by Anonymous Coward · · Score: 1

      Umm, everybody uses 1 billion = 1000 million these days, the 1 billion = 1 million million definition is long obsolete.

    2. Re:erhm by Anonymous Coward · · Score: 1

      So you're admitting America is part of the civilized world?

      That's a rare concession coming from the poor inbred eurotrash element.

    3. Re:erhm by Anonymous Coward · · Score: 0

      Except for example in the Netherlands where we use long scale.

    4. Re:erhm by Anonymous Coward · · Score: 2, Funny

      Well, sure. America is part of the civilized world... except for the rampant genital mutilation.

    5. Re:erhm by GuB-42 · · Score: 1

      In France we use the long scale but the term "billion" is almost never used. The short scale billion is called milliard and for the short scale trillions, we simply use thousands of milliards.
      Short scale trillions are so big anyways that they only seem to be used to express national debts. In science and computing, SI prefixes are preferred.

    6. Re:erhm by toxygeneb · · Score: 1

      For the first time ever I wish I had mod points!

      --
      Equal Rights, Representation, Education & Welfare
    7. Re:erhm by Anonymous Coward · · Score: 0

      Same in Germany

    8. Re: erhm by silentcoder · · Score: 1

      Interesting. In Afrikaans Miljard (which is pronounced almost exactly like milliard) is only a hundred million.

      --
      Unicode killed the ASCII-art *
    9. Re:erhm by ale2011 · · Score: 1

      In France we use the long scale but the term "billion" is almost never used. The short scale billion is called milliard and for the short scale trillions, we simply use thousands of milliards.

      Ditto for Italian. Long scale terms seem to imply a billiard is 10^15. Carambola!

    10. Re:erhm by Anonymous Coward · · Score: 0

      Well America does have a democratically elected government not a dictatorship like the Fourth Reich based in Brussels

  4. Wrong assumptions by Anonymous Coward · · Score: 0

    No project would spec the damn thing as the progression of what went before. You define your requirements now, for today or tomorrow. The mistakes of the past and obsolete functionality and requirements are irrelevant.

  5. Huge presumption by sunderland56 · · Score: 3, Interesting

    They are presuming that all of their projects are equally valuable. The GCC compiler, for instance, is widely used, and it's disappearance would put a large hole in the software world. Gnu Hurd, on the other hand.... if it disappeared tomorrow, would anyone even notice?

    1. Re:Huge presumption by Anonymous Coward · · Score: 1

      ... Gnu Hurd, on the other hand.... if it disappeared tomorrow, would anyone even notice?

      It HASN'T?!?!?!

      captcha: failsoft

    2. Re:Huge presumption by Anonymous Coward · · Score: 0

      GNU Hurd is probably not a project with which the Linux Foundation is involved...

      Also, if the GCC is such a project, then its disappearance would merely force a nice upgrade to LLVM.

    3. Re:Huge presumption by lister+king+of+smeg · · Score: 1

      those would be gnu projects not linux foundation projects which would be the Linux kernel, Xen hypervisor, and other projects

      --
      ---Saying gnome 3 is better than windows 8 not so much a compliment as it is damning with light praise.
    4. Re:Huge presumption by Anonymous Coward · · Score: 0

      Is Gnu Hurd a Linux Foundation collaborative project?

      I dunno if LF gives a shit about Hurd.

    5. Re:Huge presumption by gstoddart · · Score: 2

      Wait, what? Does the Linux Foundation own either of those two things?

      Linux isn't "every piece of Gnu software on the planet", and I seriously doubt very much the Linux Foundation either claims to own GNU Hurd, or has anything to do with it being pushed.

      Are you perhaps totally confused about what "Linux" is? I'll give you a hint ... it's the core operating system. It's certainly not every piece of GNU software, and it's definitely got nothing to do with GNU Hurd.

      --
      Lost at C:>. Found at C.
    6. Re:Huge presumption by Tough+Love · · Score: 2

      The GCC compiler, for instance, is widely used, and it's disappearance would put a large hole in the software world. Gnu Hurd, on the other hand....

      Neither is a Linux Foundation project.

      --
      When all you have is a hammer, every problem starts to look like a thumb.
    7. Re:Huge presumption by Tough+Love · · Score: 2

      Does the Linux Foundation own either of those two things?

      The Linux Foundation does not "own" any of its projects.

      --
      When all you have is a hammer, every problem starts to look like a thumb.
    8. Re:Huge presumption by Anonymous Coward · · Score: 0

      a nice upgrade to LLVM.

      And all of the architectures that are not supported by LLVM are then screwed...

    9. Re:Huge presumption by IamTheRealMike · · Score: 2

      Yes, their infographic lists "Dronecode" whatever that is, alongside node.js

      The other problem with trying to calculate the value of the Linux kernel specifically is that it counts the costs of all the drivers as well and you end up concluding that building a kernel is infeasibly expensive (reality check: there are quite a few of them out there, made by non-huge companies). If Linux was developed from scratch commercially you wouldn't attempt to develop drivers for every piece of hardware known to man all in the same source tree. You'd do what Microsoft do and define a driver API. Then the costs of hardware support are spread out across industry and no one entity ends up paying the entire cost.

      The Linux kernel guys don't do that because they prefer being able to refactor/redesign any part of the kernel at whim, even at the huge cost of having all driver development be centralised. But that's not the only way to do it.

    10. Re:Huge presumption by Anonymous Coward · · Score: 0

      And all of the architectures that are not supported by LLVM are

      not cared about by anyone.

    11. Re:Huge presumption by Grishnakh · · Score: 2

      Right, the other way is the Microsoft method where you create an API and just let everyone else write driver code for their own devices. Then you get tons of horribly-written drivers, all running in privileged mode inside the kernel, and every time one of them has a problem, you get a blue screen. It doesn't matter how great your kernel is because just one shitty third-party driver will crash it.

      This very problem has dogged Microsoft for decades now. The only ways they've gotten around it are 1) adopting part of the Linux model of making their own drivers for many commonly-used peripherals and including those as part of Windows, and 2) instituting the WHQL program to have MS test out third-party drivers and check their quality. The latter option simply isn't doable for Linux, because it requires a large, for-profit organization maintaining the OS and which is able to set up something of that scale, and it also requires the OS to already be in a market position where hardware makers are willing to pay high fees to have their drivers checked and certified by the OS vendor under this program. Almost no one is going to pay $$$$$ to have some company (or something like the Linux Foundation) thoroughly check their closed-source drivers, because Linux marketshare outside the server room is puny.

      On top of this, Linux does have a big presence in the embedded sector, but here there's loads of closed-source drivers with varying quality, and it's caused a lot of problems.

      Finally, being able to change interfaces at a whim when things change (such as when WiFi standards are amended) is a big advantage; having a fixed API/ABI makes that impossible, so you end up with workarounds like multiple API versions, which results in kernel bloat and performance loss.

      The other thing you could do is go to a pure microkernel design, but there again you get performance loss.

    12. Re:Huge presumption by KGIII · · Score: 1

      But you gain stability at that loss of performance. The dude that got the Minix going has some nice writings about microkernel designs. Given that he wrote THE book on operating systems, well, I do respect what he says. However, I don't use Minix. I generally stick with Linux or BSD - I've been enjoying GhostBSD a lot lately but the *buntu family is just so huge and handy so I'm often booted to Lubuntu.

      --
      "So long and thanks for all the fish."
    13. Re: Huge presumption by Anonymous Coward · · Score: 0

      But they also assume that companies would collaborate on common projects. In reality, if every company had had to develop its own software,there would be massive duplication of effort. How many incompatible recreations of GCC would we now have?

    14. Re:Huge presumption by Grishnakh · · Score: 1

      Yep, Minix is one of those things where it sounds good in theory, not so much in practice. There's a reason there's no true microkernel designs out there dominating any markets.

    15. Re:Huge presumption by Anonymous Coward · · Score: 0

      read much?

      the dollar figure is based upon total *lines of code* and a set development time and development cost for that code. not how "valuable" one project may be over another.

    16. Re:Huge presumption by im_thatoneguy · · Score: 1

      3) They also moved drivers into user space so those bluescreens you refer to rarely happen these days even with garbage drivers.

    17. Re:Huge presumption by Enter+the+Shoggoth · · Score: 1

      Yep, Minix is one of those things where it sounds good in theory, not so much in practice. There's a reason there's no true microkernel designs out there dominating any markets.

      Oh really! Is that so?

      https://en.wikipedia.org/wiki/...

      --
      Andy Warhol got it right / Everybody gets the limelight
      Andy Warhol got it wrong / Fifteen minutes is too long.
    18. Re:Huge presumption by Anonymous Coward · · Score: 0

      > There's a reason there's no true microkernel designs out there dominating any markets.

      Besides QNX, you mean.

  6. You know who by Anonymous Coward · · Score: 0, Insightful

    115,013,302 total lines of source code means nothing if some of it is garbage. How many lines has "He who should not be mentioned" contributed?

    1. Re:You know who by MickyTheIdiot · · Score: 1

      As much as I don't like "He who should not be mentioned," at least it is a contribution. There is some implicit agreement that the action is worth something or else it would never have been done.

    2. Re:You know who by Anonymous Coward · · Score: 0

      Who is "he who should not be mentioned"? Bennet Hasselton?

    3. Re:You know who by wodencafe · · Score: 1

      Yes, who indeed? GKH? Alan Cox? Lennart P? Kay Sievers? rms? Linus?

    4. Re: You know who by Anonymous Coward · · Score: 0

      Contributions by definition add value. Stuff that is destructive by nature i.e. everything that Poettering does, writes or influences, hence can never be called a contribution. Systemd ia a good (rather, bad) example for that kind of thing. It's a poison pill, or worse. And we should always call out Poettering as he does not deserve anything else but be shamed for he is the destroyer of a long lived and prosperous community.

    5. Re:You know who by CronoCloud · · Score: 1

      I am a desktop end-user of LInux, without any anti-systemd feelings because for me there really hasn't been much difference. But I think the above post is hilarious and gets the references right.

      You do need something like this too: "Lennkor had the aid of Fedoriant. in the poisoning of the Process Trees that enabled him to take the Sysvmarils.

    6. Re:You know who by Anonymous Coward · · Score: 0

      You know who = Voldemort

    7. Re:You know who by Ginger+Unicorn · · Score: 1

      Hans Reiser?

      --
      (1.21 gigawatts) / (88 miles per hour) = 30 757 874 newtons
  7. Weee FUD! by Anonymous Coward · · Score: 0

    With 115,013,302 total lines of source code, LF estimated the total amount of effort required to retrace the steps of collaborative development to be 41,192.25 person-years — or 1,356 developers 30 years to recreate the code base present in The Linux Foundation's current collaborative projects listed above.

    So, they're putting a "customized for one use" price tag on all the re-written Unix code that is available for purchase from many suppliers*. That alone probably bumps off half the cost, and convinces me not to care about the rest of their claims.

    *Leaving out all the other Unix inspired options that rival Linux in price

  8. Delusional by pigsycyberbully · · Score: 0

    It is just software.

    1. Re:Delusional by __aaclcg7560 · · Score: 1

      "Some bits are more equal than other bits." - George Orwell

    2. Re:Delusional by KGIII · · Score: 1

      I must confess... I'm kind of partial to my dirty bits.

      --
      "So long and thanks for all the fish."
  9. Honestly, sounds low ... by gstoddart · · Score: 4, Interesting

    If every corporation which relies on Linux as part of its infrastructure had to buy or build every piece of technology required to replace Linux, I should think on a global scale it would be far more than that.

    Because a lot of that effort would be duplicated by multiple companies .. and of course the patent litigation by all of the players who seek to claim they invented some piece of technology which predates them.

    I can believe $5 billion in this quite easily.

    Of course, I can't read the paper since I need to fill out some fscking form from, and that's not happening.

    Pity the Linux Foundation doesn't believe in open information.

    --
    Lost at C:>. Found at C.
    1. Re:Honestly, sounds low ... by Tough+Love · · Score: 2

      I can't read the paper since I need to fill out some fscking form from, and that's not happening.

      That bit of PHB genius demonstrates adequately how disconnected from the community the Linux Foundation really is.

      --
      When all you have is a hammer, every problem starts to look like a thumb.
    2. Re:Honestly, sounds low ... by gtall · · Score: 2

      My guess is the $5 Billion is fairly low. Who would organize the redone software, every two-bit company out there would contribute and then claim they owned a piece of the result. it would be a cluster-f of immense proportions. Meanwhile, the companies that currently rely on it would be SOL for further updates for security issues. Then there is the cost of companies throwing up their hands and buying closed source because every two-bit company with their closed software stack would be promising bargains like crack dealers...errr...like they currently do but now with a more captive clientele.

    3. Re:Honestly, sounds low ... by BradMajors · · Score: 4, Insightful

      Since just one company, Microsoft is earning two billion per year from Android alone. Five billion does seem low.

    4. Re:Honestly, sounds low ... by Anonymous Coward · · Score: 1

      Of course, I can't read the paper since I need to fill out some fscking form from, and that's not happening.

      Pity the Linux Foundation doesn't believe in open information.

      Direct link to the file: http://go.linuxfoundation.org/l/6342/pub-cp-cost-estimate-2015-pdf/2vbgpm

    5. Re:Honestly, sounds low ... by Anonymous Coward · · Score: 0

      so fill it out with bogus information that also lets them know you don't want to fill that kind of stuff out like the rest of us do

    6. Re:Honestly, sounds low ... by EndlessNameless · · Score: 1

      You can fill it in with complete bunk.

      Maybe if they see enough downloads from Mr ABC DEF at abc@def.com they will realize no one is interested in providing them personal information.

      --

      ---
      According to the latest ruleset, this post should be modded as Vorpal Flamebait +5.
    7. Re:Honestly, sounds low ... by Anonymous Coward · · Score: 0

      You can fill it in with complete bunk.

      Maybe if they see enough downloads from Mr ABC DEF at abc@def.com they will realize no one is interested in providing them personal information.

      Direct link to the file: http://go.linuxfoundation.org/l/6342/pub-cp-cost-estimate-2015-pdf/2vbgpm

    8. Re:Honestly, sounds low ... by Anonymous Coward · · Score: 0

      Because a lot of that effort would be duplicated by multiple companies

      True enough. But I think the cost of that duplication would be far greater than you might imagine at first.

      There are a huge number of standards that Linux defines -- just look at how many APIs and ABIs there are. Every one those standards promotes easier inter-operation of software pieces. That ease of inter-operation scales up just like the network effect scales up -- IIRC, the total value is roughly in proportion to the square of the number of components.

      If everyone was always reinventing the wheel on all those APIs, the explosion of incompatibility would account for by far the greatest portion of the value lost. For example, it would be doable for a large company to design a new set of APIs that duplicate what the Linux standard lib*.so libraries do, but it would be absolutely devastating to the industry as a whole to have 100 duplicate incompatible proprietary APIs at that level.

    9. Re:Honestly, sounds low ... by Anonymous Coward · · Score: 0

      If every corporation which relies on Linux as part of its infrastructure had to buy or build every piece of technology required to replace Linux, I should think on a global scale it would be far more than that.

      Because a lot of that effort would be duplicated by multiple companies .. and of course the patent litigation by all of the players who seek to claim they invented some piece of technology which predates them.

      I can believe $5 billion in this quite easily.

      Of course, I can't read the paper since I need to fill out some fscking form from, and that's not happening.

      Pity the Linux Foundation doesn't believe in open information.

      For sure that is low.

      Here's the point though. When even a home user installs Linux... they get immediate access to $5+ billion dollars of software for free.

      And it isn't Windows Global Spyware.

      distrowatch.com

  10. Monetization by Anonymous Coward · · Score: 0

    Open source is great for reducing development costs. There are so many companies that just put together open source software and sell it as their branded solutions.

    But there are not that many Open Source contributing companies that turn a profit from it. Red Hat, Oracle do, and presumably Canonical and SUSE. I don't know about MongoDB, they are still at the VC stage as far as I know. Same with other database and big data solution providers, they look fragile at their best. Some like Facebook and Google use it extensively for their infrastructure, so they "give back" a lot. Others like Intel and Samsung want it to work on their products, so they contribute a lot, for example, to the Linux Kernel.

    So Open Source is great for companies in general, maybe a bit less for those actually making the OSS. But I don't know how great it will be for developers in the long run in the sense of commanding higher salaries and the number of job openings. Maybe we are in some kind of Golden Age in that regard. A lot of the middle class is based on "supply management", which is currently evaporating quickly in many areas.

    1. Re: Monetization by Anonymous Coward · · Score: 0

      Modem/router makers created oss system for their equipment and I would assume they saved a lot of money doing that.

  11. COCOMO calculation and its drawbacks by __roo · · Score: 5, Informative

    For those who don't know, COCOMO is an algorithm that was developed in 1981 by Barry Boehm for estimating the cost of building software (typically in person-hours). The numbers in the article were generated by the basic COCOMO calculation in David Wheeler's free SLOCCount toolset.

    One drawback is that SLOCCount uses the basic COCOMO calculation, which is based on historical data gathered by Boehm in 1981. Here's a COCOMO-81 calculator in case you want to play with your own code. Sometimes its estimates are pretty good, but I've sometimes found that applying line counts from my projects in some modern languages (especially functional ones like Scala) throw it off. That could definitely affect the "1,356 developers 30 years" estimate in the article.

    Wheeler has a good discussion of COCOMO in SLOCCount if you want to learn more about it.

    1. Re:COCOMO calculation and its drawbacks by gstoddart · · Score: 2

      That could definitely affect the "1,356 developers 30 years" estimate in the article.

      Sure, but look at it this way: way more developers than that have been working away on Linux for the last 20+ years.

      My experience with people trying to re-write a similar set of functionality from scratch, and covering all of the corner cases, exceptions, audits, and bug fixes ... that tells me that it takes a LOT longer to write something like that.

      So, ignoring the userland stuff, and things which hook into Linux, it's still a massive undertaking to write it, test it, verify it, find all the issues, identify and fix exploits ... all of those things take a lot of time.

      I don't think it's all that unrealistic to think that trying to rebuild it from scratch would be a massive undertaking, costing huge sums of money ... because it already was a massive undertaking. A lot of it might have been done without someone directly paying for it, but it took a hell of a lot of resources.

      But the 20+ years of who knows how many people which have gone into Linux isn't something you could reproduce quickly. I don't buy that for a minute. You'd have security holes, crash conditions, optimizations, errors, or huge gaps in functionality.

      So, in a roundabout way ... thanks to all the people who have made Linux what it is. Because it's far too easy to undervalue it or take it for granted.

      --
      Lost at C:>. Found at C.
    2. Re:COCOMO calculation and its drawbacks by Junta · · Score: 1

      I also wonder about how well the concept would scale up..... Very complex projects I've found have very little correlation between how costly it was to implement and the lines of code involved. I think this would be a case where the complexity of the task is not well represented by lines of code (lot's of code was created and eventually deleted that still represents work that would be likely to occur for an organization seeking to indepentently implement the same sort of stuff).

      --
      XML is like violence. If it doesn't solve the problem, use more.
    3. Re:COCOMO calculation and its drawbacks by Anonymous Coward · · Score: 0

      What drawbacks are you suggesting? That it's overcounting old code, or undercounting newer C99/C11 code, or that the man-hour estimates for post-1981 languages aren't up to date?

    4. Re:COCOMO calculation and its drawbacks by tomhath · · Score: 2

      That it's overcounting old code, or undercounting newer C99/C11 code, or that the man-hour estimates for post-1981 languages aren't up to date?

      All of the them. COCOMO says "tell me how many lines of code there will be in project and how many LOC/HR your developers will write and I'll tell you how long it will take". Well, duh.

    5. Re:COCOMO calculation and its drawbacks by meta-monkey · · Score: 1

      Their estimate's a bit off. They didn't factor in the cost of each developer's allotment of Mountain Dew.

      --
      We don't have a state-run media we have a media-run state.
    6. Re:COCOMO calculation and its drawbacks by Anonymous Coward · · Score: 0

      Well it is a little more precise, with factors like "How stupid are your developers, anyway?" and "Just how smart do you think you are in the first place?"

    7. Re:COCOMO calculation and its drawbacks by KGIII · · Score: 1

      I don't contribute code - I will, if you want but rest assured that you do not want that - trust me on this. I've done lots of coding, lots. Eventually I hired capable people to do it for me and eventually they pretty much told me to stop helping. I listened. However, I donate. I donate a lot to a number of the various FOSS folks. I figure it is what I can do and that I must do something. I think my next big donation (probably silent) will be one of the bug bounty programs. I don't have any particular bugs that need fixing but, well, they do. Somehow I manage to generally escape such or just work around it without complaint.

      --
      "So long and thanks for all the fish."
  12. in b4 trolls by MickyTheIdiot · · Score: 1

    "But my time is worthless, that's why I use open source."

    Seriously, though... the world works on open source these days. I would say is another bogus calculation and the real harm would be incalculable.

    Or take it another way... this is theoretical enough to be useless. Because the source is OPEN it's impossible to eradicate. You nuke one code repository and five more spring up in its place.

    As always, since the very nature of these projects mean you don't have a marketing teaming going "rah rah" all the time in background like Microsoft does people don't KNOW the world runs on open source projects...

  13. Hey, that's a nice infrastructure you got there... by jpellino · · Score: 1

    lotta rogue apps come running thru here. Be a shame if one of them, you know... No, no - I'm not saying nothing, I'm just saying. (It's a joke. What they've accomplished in software is stunningly good.)

    --
    "Win treats sysadmins better than users. Mac treats users better than sysadmins. Linux treats everyone like sysadmins."
  14. Imputed Income! by deck · · Score: 1

    Oh great, now the information on taxing FOSS has been created. The government can now demand to know how much FOSS a person or company is using and then tax them on the "value" of it even though you paid nothing (and for individuals not earning anything from it).

    If you don't know how a government does imputed income, let me cite an example that almost got done. The current US "regime" wanted to charge home owners who had taken a mortgage on a house years ago and were making relatively small payments by current rates, the difference between what their house would rent for (if it was more than the mortgage payment) and the mortgage payment as imputed income. Yes, if you were paying $500 a month and the house could rent for $1500, you would have to add $12000 to your annual income in "imputed" income.

    Now take that and apply it to FOSS. One single distribution in use could be imputed to be worth thousands of dollars. Microsoft, Oracle and others would love to latch onto that and use it to kill FOSS if they can only get the government to do their bidding. The ability to do this in other countries may vary but probably not by much.

    1. Re:Imputed Income! by Anonymous Coward · · Score: 0

      That's not a citation, it's a description, which, without a citation, is just FUD.

    2. Re:Imputed Income! by murdocj · · Score: 2

      The current US "regime" wanted to charge home owners who had taken a mortgage on a house years ago and were making relatively small payments by current rates, the difference between what their house would rent for (if it was more than the mortgage payment) and the mortgage payment as imputed income. Yes, if you were paying $500 a month and the house could rent for $1500, you would have to add $12000 to your annual income in "imputed" income.

      This sounds like extreme BS. Care to cite something other than Internet rumor?

    3. Re:Imputed Income! by Grishnakh · · Score: 1

      That sounds like BS at the Federal level, but it sounds exactly like something that certain shitty little localities would want to try.

    4. Re:Imputed Income! by deck · · Score: 1

      Since you two are so bothered by truth, here are some citations:

      Working Paper Series, Congressional Budget Office -- Taxation of Owner-Occupied and Rental Housing

      This is from a Democrat Majority U.S. Congress along with a Democrat predominant Executive Branch (President and Departments). See page 3.

      Taxing Homeowners as if They Were Landlords

    5. Re:Imputed Income! by Anonymous Coward · · Score: 0

      The current US "regime" wanted to charge home owners who had taken a mortgage on a house years ago and were making relatively small payments by current rates, the difference between what their house would rent for (if it was more than the mortgage payment) and the mortgage payment as imputed income. Yes, if you were paying $500 a month and the house could rent for $1500, you would have to add $12000 to your annual income in "imputed" income.

      This sounds like extreme BS. Care to cite something other than Internet rumor?

      My Father in Law forwarded me that email too, along with the one about how Obama was a secret gay Moslem radical from Kenya while going to Black Radical Church with Reverend Wright and was behind the 9/11 bombing and is a part of a Chinese plot to take our guns, enslave white women and burn bibles. But Trump will save us by cutting taxes for him which is crucial because he's going to hit the SuperJackpot with the money get gets from a Nigerian Prince since he'll keep all the money and not wire any back once the Prince sends it over, to teach that sucker a lesson, because 'Murica! Also Obama can't be trusted because he's an atheist too. Somehow.

    6. Re:Imputed Income! by Anonymous Coward · · Score: 0

      That looks like a discussion document, not policy. As someone working in a branch of government in another country, I can assure you that there are lots of examples of stupid policies considered as discussion documents. This is usually because a newly arrived elected representative or senior official who doesn't understand a subject puts forward a pet idea (sometimes something they got the previous night while talking with friends over a drink) and wants it costed, and have the influence to do it. Most of these ideas die in the cold light of day, a few get taken seriously, and some are implemented. Sometime these cause mayhem or stupid wars. Similar things happen in private industry as well, but unlike government these have little tradition of public disclosure and we rarely hear about them until the mayhem actually occurs.

  15. On the flip side... by Junta · · Score: 4, Insightful

    They said it would take approximately 30 years for approximately 1300 developers to get there. We know because we have an idea of how things evolved that estimate is actually a bit short. Some of that codebase is about 30 years old, and well more than that many developers have contributed. Things have been done, discarded, redone. The estimate is actually a pretty optimistic one that assumes the developers get it 'mostly' right the first time when actual history has had many many dead ends that caused a total rethink. One would expect the same out of a private endeavor. So there's some balancing out.

    --
    XML is like violence. If it doesn't solve the problem, use more.
    1. Re: On the flip side... by silentcoder · · Score: 1

      The LF codebase has nothing older than the kernel which is 24 years old. But they do have contributions from far more than 1300 developers in that codebase.

      --
      Unicode killed the ASCII-art *
  16. Verbs incredibly valuable by Anonymous Coward · · Score: 0

    > Everybody recognizes that open source software incredibly valuable

    Editor incredibly valuable too.

  17. Or in other words... by Maury+Markowitz · · Score: 1

    > the price they've come up with is eye-popping: $5 billion.

    Apple claims to have sold 13 million iPhones on launch weekend. Assuming an average price of $800, that's 10 billion in two days.

    So this doesn't impress me much. Or at all. I suspect its at least an order of magnitude higher than their estimate.

    1. Re:Or in other words... by Hognoxious · · Score: 1

      Right. Totally valid comparison, because the hardware grows on trees.

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    2. Re:Or in other words... by Moof123 · · Score: 1

      It is a Big Round Number that impresses until put into context. I am not sure what they are setting out to accomplish other than to come up with a metric so they can stick their thumbs in their rainbow suspenders and come off as even more condescending and self righteous.

  18. Seems Low by EndlessNameless · · Score: 2

    Since most companies would either develop proprietary solutions or buy at a substantial markup from an establish publisher, the actual cost to replace all that software would be much, much higher. And if an established organization offers a replacement, it will likely have competitors---which again gives a duplication of effort, even if it is much smaller duplication than proprietary redevelopment of the functionality. This is not addressed at all in the paper.

    They do acknowledge that failed or superseded code is not included in their analysis, and there was certainly developer time spent on code that is not a part of the project, either because it was culled or never made the cut to begin with.

    Given both of those factors, the $5 billion figure is a very low best-case value. The practical cost of replacement would be monumentally higher once the mundane practicalities come into play.

    --

    ---
    According to the latest ruleset, this post should be modded as Vorpal Flamebait +5.
    1. Re:Seems Low by mlw4428 · · Score: 1

      > the actual cost to replace all that software would be much, much higher.

      I'm not sure on that. There are the BSDs out there and Windows still does exist (may not run on every device sure, but there are other low cost/free/open source embedded OSes that would). The biggest cost would be driver development/market adoption. But if we take into consideration the cost that companies/individuals (paid at an average market rate) spent doing it for Linux, then it's probably not far off of the mark. And since Linux is open source and the specs are readily available, it wouldn't be too hard to write a compatibility layer (much like BSD has) to run the Linux apps. If you could achieve a compatibility layer the I'd imagine that the perceived value of Linux could drop significantly.

    2. Re:Seems Low by EndlessNameless · · Score: 1

      Did you read the article?

      The way they're talking about replacement cost, it only really makes sense if they're talking about building again from scratch.

      I assume existing applications would be developed to add all the lost functionality. If that's the game---a more practical take on "replacement" of the open source code---then you have to include integration and testing costs. Plus any opportunity costs for "lost" functionality that was not deemed worth reimplementing---because some things are very hard to do well, and the next developer might not bother unless there is overwhelming demand for it.

      So even if you setup different goalposts compared to what the study examined, it's still going to be expensive. The only difference is there's just no widely-established standard for estimating how expensive.

      --

      ---
      According to the latest ruleset, this post should be modded as Vorpal Flamebait +5.
    3. Re:Seems Low by mlw4428 · · Score: 1

      I suppose I was thinking of product developers (say, like Android) starting over "from scratch" without the Linux OS. I agree with the rest of your points.

    4. Re:Seems Low by Anonymous Coward · · Score: 0

      If you use the standard government estimations, this figure is off by at least a factor of 20 (meaning a minimum of 100 billion dollars would be required to replace all of the code in the Linux Foundations Code Repository. That's for the United State Alone. World wide, that estimate would easily climb to 2.5 Trillion Dollars minus the estimated pirated values.

    5. Re:Seems Low by KGIII · · Score: 1

      If you frequent torrent sites you'll find you can, indeed, pirate Linux. I've seen a number of RHEL torrents but I've never tried it. I should give it a shot in a VM sometime.

      --
      "So long and thanks for all the fish."
  19. Only been worth hundreds to me by EzInKy · · Score: 1

    But I guess if enough others save hundreds as well that figure can easily be in the billions globally. Still, it is the hundreds saved that are important to me.

    --
    Time is what keeps everything from happening all at once.
    1. Re:Only been worth hundreds to me by KGIII · · Score: 1

      It costs me a lot but that's because I donate more than I'd pay for a proprietary OS. I'm not really in it to save money, however. I'd write code but, frankly, you don't want me to do that.

      --
      "So long and thanks for all the fish."
  20. I call BS by Anonymous Coward · · Score: 1

    Just simply calculating 5B / (1356*30) you get approximately $122K per year. Bull shit. No fucking way 14 year old Billy from Boise in his mom's basement is making any money, let alone 122 grand.

    1. Re:I call BS by KGIII · · Score: 1

      I forget the number but a good majority of the Linux code comes from paid developers working on their company's dime. Lots of companies are pushing code up stream these days. It's not like it used to be and that's a great thing.

      --
      "So long and thanks for all the fish."
    2. Re:I call BS by Anonymous Coward · · Score: 0

      I agree. $122K average for each of the 41,000+ person years seems pretty excessive. How much of the code really requires a top-notch programmer?

    3. Re:I call BS by Infiniti2000 · · Score: 1

      This is true, but consider that 122K is on average. This means for every person in school out there contributing for free, we have others making 244K per year. If it were 10% free development, then the average for the others is 136K. The average salary for a software engineer in the USA is 94K, so something is fishy.

  21. rebuild or develop from scratch or... by tomhath · · Score: 1

    Or, more likely, switch to FreeBSD and forget Linux ever existed.

    1. Re:rebuild or develop from scratch or... by iamgnat · · Score: 1

      Or, more likely, switch to FreeBSD and forget Linux ever existed.

      This was along my line of thinking. Few are going to try to rebuild most of those things if they all of a sudden disappeared. They are simply going to another vendor that already offers a similar product.

      There is certainly a cost to all of that and it would be painful, but I somehow suspect that the price of switching would be far less than their estimate. Well, unless you went to Oracle for everything...

  22. How much if outsourced to India? by Anonymous Coward · · Score: 0

    Is that $5billion if US developers are being paid (on average) $100k/yr to do it?

    If so, can we outsource the rewriting of all that source code to India or some other location for a cheaper outcome?

  23. Screw you. by Anonymous Coward · · Score: 1

    Trying to cheat me out of moneybits.

    1 billion = 1024 million.

    1. Re:Screw you. by unixisc · · Score: 2

      This!!! They should recalibrate everything from base 10 to base 16, so that computers save cycles doing BCD conversions

  24. $5! by Anonymous Coward · · Score: 0

    my newsreader truncated the headline an stated the value as $5.
    $5 for free software seems to be a bargain.
    Had to laugh. /sarcasm

  25. No, way more. by EmperorOfCanada · · Score: 3, Interesting

    The costs also need to consider all the dead ends and bad decisions. How much code was built that was never injected into the system. I suspect that many Linux developers have conjured up some really long and interesting code that they then never submitted. They threw it out and started again.

    Then there is the quality of the programmers. The few programmers that I have met who contributed to the Linux codebase were pretty damn kickass. Thus hiring them would not only be expensive but really hard. Most of them wouldn't work for most companies as they know they are the elite of the elite and can pick and choose their surroundings.

    Also Linux contributions are often a resume builder. Thus many junior but very very good programmers will do some Linux contributions which then makes them look cool. The reality is that they don't want to work on Linux but want some other job, such as the games industry. This is a double problem. Some company hiring for their 5 billion dollar project would never have hired them because they had crap resumes, and these kids didn't want to work on Linux and thus wouldn't accept a job working for a big boring company building an OS.

    Then there is the urgency factor. Many critical tiny bits of Linux were built by people with a specific problem. They didn't have a Linux driver for their 10,000 machines with the L257B Arcnet card. Thus they dove in and modified the driver for the L256A arcnet card just enough to make it work. But where would that kind of bug/feature have been prioritized by a corporation? Plus again the person doing this brought a skillset that was obviously very good for that problem but otherwise might have been a terrible hire for the project.

    Then there are the various OS distributions that compete. Not all Linux decisions have been good ones. Thus different distributions follow different paths resulting in winners and losers for various aspects of the system. Over time the winners end up spreading across the distributions and the losers just sort of fade away. Even the classic Gnome vs KDE has resulted in each becoming better. So one must count the costs of developing both Gnome and KDE.

    This last one even extends out to other Open Source OS projects such as BSD in that code from that project end up in Linux as well as providing competition.

    Then there is the whole build the wrong thing problem. Linux has evolved steadily to meet the demand of its users. But a corporation would build a product that would meet the demands of its marketing department. Thus any corporation building Linux wouldn't build Linux. They would typically build something like Windows or OS/2; Operating systems that were designed to create an ecosystem for selling other crap made by that company and locking their customers in.

    So while it is interesting to say such a huge number, I personally think that the number would be far far larger as to put together such a talent pool would probably be a mega project in itself over and above the actual paying of that pool and the other development costs.

    1. Re:No, way more. by Grishnakh · · Score: 1

      Even the classic Gnome vs KDE has resulted in each becoming better.

      No it hasn't. Gnome has been getting worse ever since 1.0. There's certainly been lots of development work on it since those days, but it's only made it worse, not better. It's no different than Windows: everything GUI-wise since Vista has been a step backwards.

    2. Re:No, way more. by EmperorOfCanada · · Score: 1

      Then, by that standard, KDE may have learned what not to do. An important lesson that I have taught myself many times.

    3. Re:No, way more. by Jack9 · · Score: 1

      > I suspect that many Linux developers have conjured up some really long and interesting code that they then never submitted

      All programmers do this. That's part of the development cost. I think you meant potential Linux developers that never contributed. We don't know about the code that we don't know about. Ok? What's more important is the 5 billion completely ignores the trillions that would be made off of licensing fees...you know, how they would have paid these theoretical costs. Since the US BEA calculates the GDP based on potential Tech valuation, might as well use potential value in the Open Source calculations.

      --

      Often wrong but never in doubt.
      I am Jack9.
      Everyone knows me.
    4. Re:No, way more. by Moof123 · · Score: 1

      But 30 redundant and mostly unused distros are surely 30x more valuable than one that people actually use...

    5. Re:No, way more. by EmperorOfCanada · · Score: 1

      Except in this case I suspect that unlike paid programmers who eventually have to submit even if it is sort of crappy but works, the non paid Linux programmers might create their new marvel but realize that it is crap and the world never hears about it.

      Also, unlike in a large company with assignments, there are probably 20 programmers working right now on some cool feature or bug. But only one of them will get their submission in or the code will be submitted and then replaced by any solutions better than it that soon follow.

    6. Re:No, way more. by EmperorOfCanada · · Score: 1

      The key is that many of the distros over the years often had some cool feature that may have been adopted by the main distros. Maybe a better installer, or package manager. Many were just a huge waste of time for all involved. So how do you calculate the value of some group putting together an entire and innovative distro but the only thing remaining of it today might be a slightly better installer in the main distros?

      Yet all of today's main distros were some obscure distro in their distant pasts.

      My first distro was one called Slackware. I remember the extreme pain in getting that thing to work. But when it did I pretty much danced around the room having my own Unix system. To me that was something only huge companies and universities had at the time.

  26. Not much value then by Anonymous Coward · · Score: 0

    Apples profit for one quarter last year was MUCH BIGGER., so you are basically saying after all these years your code is worth 2 month profit from Apple.

  27. 1/3 NASA yearly budget by MooseTick · · Score: 1

    So you could take about 1/3 of NASA's yearly budget and recreate it all from scratch. Just think of what could be available if NASA was defunded for 5 years and that money went into a national open source development project where everything created would be free to the world.

    Of course, imagine if we did the same with 1/2 of the US military budget. I suspect you'd run out of developers to hire before you ran out of money. And the pay for developers would be higher than airline pilots.

  28. This is the stupidest estimate. by 140Mandak262Jamuna · · Score: 1
    It would cost AT LEAST 5 billion to recreate the code being used.

    Amount of testing needed to achieve the same level of reliability and interoperability ? Could easily top 500 billion dollars.

    No, it is not hyperbole. Look at the expense most companies are going through to maintain ageing old code running in mainframes or the code running on WinXP and IE6 and ActiveX control. If you look at the man years used to develop that code, it might be X. To rip it out and replace it? It has no relationship to X. It all depends on how many other modules depend on it.

    It is true for everything, not just code. Cost of constructing Tappan Zee bridge would bear no relationship to the cost of blowing it down and rebuilding a replacement in situ. The cost of service interruption alone is going to exceed the original investment by several times over.

    --
    sed -e 's/Chuck Norris/Rajnikant/g' joke > fact
  29. COCOMO by Bill_FFR · · Score: 1

    I never found COCOMO particularly useful for cost predictions because you guess SLOC Instead of guessing FTEs. Reversing the process when you know the SLOC still has problems because COCOMO is nowhere near being reliable if the SW involved more than screen to database and reverse, such as significant math.

  30. That's part of the upgrade. by tlambert · · Score: 1

    a nice upgrade to LLVM.

    And all of the architectures that are not supported by LLVM are then screwed...

    That's part of the upgrade.

  31. It's only 115M lines of code. by tlambert · · Score: 1

    It's only 115M lines of code.

    My calculation on that comes out closer to $1.3B for a 5 year project to replace all of it.

    With a much smaller number of highly dedicated people who are 3X as expensive as the average software engineer in Silicon Valley, I think it'd be possible to drive the number down closer to $790M and 2 years.

    The people would need to be dedicated, and the project would need to be driven by (in effect) a dictatorial ass whom everyone has agreed to follow to the ends of the Earth. In other words, a rather strict hierarchy.

    Oh yeah... the project would have to be operated Cathedral style, and not use most "agile" techniques.

    1. Re:It's only 115M lines of code. by Anonymous Coward · · Score: 0

      Writing hardware drivers / kernel code is a bit more time consuming than writing a database application. Did you take that into account?

    2. Re:It's only 115M lines of code. by tlambert · · Score: 1

      Writing hardware drivers / kernel code is a bit more time consuming than writing a database application. Did you take that into account?

      You mean like when I personally wrote nearly a million lines in the Mac OS X kernel, over a period of several years, in order to get it UNIX certified?

      Yeah, I took that into account.

      Perhaps not enough? I should probably reduce that cost estimate, given that pretty much any dink can write user space code and get it to work, and we are mostly talking about user space code...

    3. Re:It's only 115M lines of code. by angel'o'sphere · · Score: 1

      Perhaps you should write a book about your ideas how software is written.

      When COCOMO was developed we had ideas about productivity in software development like this,
      per day a developer writes about:
      25 - 100 lines of code in user applications
      5 - 10 in service software, like specialized editors, TCP/IP stacks etc.
      < 1 line of code in system software, especially kernels.
      And this is independent of programming language used
      E.g. if you care to write your software in assembler, in the long run a kernel developer will write one single statement per day. If he uses C it will burn down to half a dozen or a dozen assembly statements per day. Using Lips / SQL or 4GLs, especially on the user application level boosts productivity by a factor of 1000 and more.

      Anyway, your idea how to burn down the costs is just ridiculous. And I bet my ass and my balls that the original estimate is off by a factor of ten, minimum. Because they likely did not judge the projects into the required "category" mentioned above.

      1000 lines in the linux kernel are more complex than 1000 lines code in a C compiler, which are more complex than 1000 lines in 'vi', which are more complex than 1000 lines in 'ls'.

      Your idea that a dictatorial ass could direct such a project is just nonsense. It is simply to complex for a single person. Also you seem not to grasp what agile is about. Agile projects, if they work, are usually much faster, which implies cheaper, than "traditional" ones. That is why most people work agile in our days, well, in my part of the world.

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    4. Re:It's only 115M lines of code. by tlambert · · Score: 1

      Perhaps you should write a book about your ideas how software is written.

      When COCOMO was developed we had ideas about productivity in software development like this,
      per day a developer writes about:
      25 - 100 lines of code in user applications
      5 - 10 in service software, like specialized editors, TCP/IP stacks etc.
      < 1 line of code in system software, especially kernels.
      And this is independent of programming language used

      These stats are largely inaccurate for modern coders, who are much more productive than if they were writing their code in IBM BAL. If you have a modern coder writing at this rate (on average), then you should likely fire them, and hire someone who can code, instead. The "on average" is because you should spend 90% of your time planning and 10% of your time coding.

      On a project (The Whistle InterJet), I wrote a Fetchmail replacement to work around a number of issues that the author felt were unnecessary to fix, and refused to incorporate as bug fixes. As gravy on the side, it got us out from under the GPL on the code, so we didn't have to carry around local patches.

      The major specific issue was not reverse time-ordering of the "Received" timestamp line being used to identify an addressee -- Fetchmail overrode earlier "for" values as it moved forward through the message, which frequently lost information, and allowed faked headers to override a destination, in order to abuse Fetchmail as a remailer for SPAM.

      The resulting production code was a little over 22,000 lines of code, and was written in a period of 2 weeks of normal 5 day work weeks. That was 1,100 lines of code a day. And yes, I ended up with tendonitis, and had to wear wrist braces off and on for a while after that, after that much typing.

      Anyway, your idea how to burn down the costs is just ridiculous.

      And yet... Mac OS X is UNIX certified, and Linux is not.

      And yet... I was tech lead on the team of 6 full time people that did it, and, in aggregate, wrote more lines of code for Mac OS X Tiger than the rest of the Core OS Kernel team and the Core OS user space team wrote for that same OS release, combined.

      Yes, we cut through an metric assload of red tape in order to do it,, and we had the dictatorial hammer of a $200M lawsuit to pound people on the head to enable us to do it. In other words, in a lot of cases, with the aid of Apple Legal,, and the backing of upper management: we were dictatorial asses. If we had to change an API, and it broke your project as a consequence of you using -Werror: you got to fix your project, because the consequences of us not making the change were $200M out of Apple's wallet, and so our hammer was bigger than yours.

      I have a number of very, very good friends who were hit by this hammer; but when you work in a corporate environment, one of the things you are paid for is to put the company's good above your personal sensibilities. The other major thing you are paid for is to get along amicably with people you would never work with, were it not for the fact that you were being paid to work with them.

      In other words, unlike in volunteer Open Source, where you bike-shed, bicker, and kingdom-build to the point of process ossification, you have your part, you do what you are paid to do, and the product ships, as the product was intended to ship.

      The point is: there are assloads of red tape between doing a mediocre job, and doing great things, and you merely need to enable people to do them.

      And I bet my ass and my balls that the original estimate is off by a factor of ten, minimum. Because they likely did not judge the projects into the required "category" mentioned above.

      No, they only mentioned the Linux Foundation code, the 115M lines. And they did it to emphasize what they perceived as the value of the code.

      The "required" ancillary code doesn't matter, because you could just

    5. Re:It's only 115M lines of code. by angel'o'sphere · · Score: 1

      No, they only mentioned the Linux Foundation code, the 115M lines. And they did it to emphasize what they perceived as the value of the code.
      My Point here was that this code neeeds to be broken down into different categories of complexity. I fear they only used a "Default category"

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    6. Re:It's only 115M lines of code. by tlambert · · Score: 1

      No, they only mentioned the Linux Foundation code, the 115M lines. And they did it to emphasize what they perceived as the value of the code.
      My Point here was that this code neeeds to be broken down into different categories of complexity. I fear they only used a "Default category"

      Complexity distinctions are rather specious; let me explain.

      Yes, a coding error in an OS can crash the whole machine. But at the time the lines of code stats were written, most computers were not running a protected mode OS, and therefore, a coding error in *any* program could potentially crash the entire machine.

      By that token, they've overestimated the value, by treating everything as if it could crash the machine. Unless we relax the criteria to "could crash the machine and/or result in a security vulnerability", in which case we are back to all code having the same level of impact on the machine as all other code. Security was pretty much not an issue back then, because there were no such things as "bad actors who did not just crash their individual machine, or, on a multiuser system, had their account suspended until they talked to someone with a scowl on their face, and received a stern warning".

      Also, I will claim that programmers who learned to code when anything they did could crash a machine (and yes, I've crashed mainframes dozens of times with user space code, back in the day, taking everyone's programs with mine -- and had mine shot down the same way) learned to be a hell of a lot more careful coders than the generation who grew up with "if it crashes, it'll only kill itself, and we can just look at the core dump". In other words, they were better coders because they had to be.

  32. You dont have to re-write everything, sheesh! by Anonymous Coward · · Score: 0

    Just use what's already out there commercially..

    In that same code proposal they're probably re-writing the internet.

  33. COCOMO by Anonymous Coward · · Score: 0

    I learned about COCOMO in university in my software engineering classes. This is the first time I ever heard about it being used concretely.

  34. Done in one month. by DidgetMaster · · Score: 1

    All you need to do is hire 494,304 programmers (41,192 x 12) and you could replace it all in a single month. Right??? See how simple math works.

  35. I need a Government quote by Dareth · · Score: 1

    What would it cost for the US or UK govt to try to duplicate this code base?

    --

    I only look human.
    My mother is a halfling and my dad is an ogre, so that makes me an Ogreling
  36. Summary confuses value with cost by Registered+Coward+v2 · · Score: 1

    Just because it would cost $5 billion to replicate the c code doesn't mean its value is $5 billion. Some could be worth a lot more that the replication costs, and some total worthless despite huge replication costs.

    --
    I'm a consultant - I convert gibberish into cash-flow.
  37. Cost of development... not actual value. by Anonymous Coward · · Score: 0

    Just look at systemd and gnome, expensive to make but totally worthless.

  38. Certainly wrong... by coldie · · Score: 1

    We all understand the mythical man-month issues here, but Microsoft alone employs around 50,000 software engineers (Google 30,000). If everything done at the linux foundation is equal to less that the output of Microsoft for one year (or google for less than 16 months), there may either be a problem with your numbers, or with the entire model of open source. I'm going to assume the issue is the models...

  39. Great for employment by Anonymous Coward · · Score: 0

    I must have an evil mind, because my first thought was... rewriting this, and debugging the result, would create a *lot* of jobs for coders. Not to mention being great fun.

    So, just for fun, imagine if we could somehow magically retract all of this code from circulation, then as a group refuse to write it again for free but rather charged for our services. It would be worth it to hear the screams from management alone :)

    (yes I know, I know, Ayn Rand got there first with that bloody awful, damn near unfinishable mess of a book and spoilt it for everyone, but it's a fun fantasy none-the-less).

  40. So... by msobkow · · Score: 1

    That works out to 8238450 work days of programming (presuming 50 week years.)

    That means they only expect a programmer to produce 1396 lines of code per day.

    It would seem they're over-estimating the cost of their projects -- even back in the early '90s an "average" programmer produced 2000 lines of code per day, and that was before the advent of most of the modern debugging and IDE technology that speeds up the process, included time for builds which used to run for hours or days instead of minutes, and involved a lot of manual processing to integrate code from different developers because versioning tools were so primitive (RCS days.)

    --
    I do not fail; I succeed at finding out what does not work.
  41. burried shovel by holophrastic · · Score: 1

    So, in a commercial environment, it would cost $5 Billion of commercial developers being paid a proper wage. I get that. But in this day and age, if you wanted to build that sort of thing, you wouldn't hire developers commercially. You'd create an open source project and let the developer community at large assist in your project.

    In doing so, it would cost far less. I cite, as my proof-of-concept example, an organization called the linux foundation, which has 115,013,302 total lines of source code and didn't spend $5 billion to get there.

    I used to wonder how I'd dig up my shovel, without my shovel. Now I wonder how I buried my shovel, without my shovel.

  42. eye popping? by Barlo_Mung_42 · · Score: 1

    That seems low honestly. That's pocket change to the big fish.

  43. Dr. Evil is for cows. by Anonymous Coward · · Score: 0

    Dr. Evil is for cows.Cows say MOOOOOOOO.MOOOOOOOOO.MOOOOOOO.MOOOO says the cows.You evil cows.