[amadvance]

The linked article says something different:

'We first estimate the supply-side value by calculating the cost to recreate the most widely used OSS once. We then calculate the demand-side value based on a replacement value for each firm that uses the software and would need to build it internally if OSS did not exist. We estimate the supply-side value of widely-used OSS is $4.15 billion, but that the demand-side value is much larger at $8.8 trillion.'

[abtinf]

The methodology used in the underlying paper is, to put it generously, not even wrong. Way past “assume a spherical cow” territory.

It supposes you could simply hire programmers to build OSS from scratch.

If you have ever worked on a large project in a corporation, you instantly know how shockingly ignorant this is.

Hint: many of them end in failure and are never released at all.

Then there are the massive amplifications that happen due to the mere existence of open source: learning, spreading of ideas, reusable tooling, and more.

Has any business school ever produced a paper worth a damn?

https://www.hbs.edu/ris/Publication%20Files/24-038_51f8444f-...

[jvanderbot]

As you say, whatever the real cost is, it's much higher than one that supposes every company could reproduce F/OSS. How amazing then, that even in this hypothetical universe where everyone could, we still wouldn't want to due to the enormous cost.

Providing a lower bound on value, and furthermore one that is astronomically high, is extremely useful as an eye-opener. This is a useful result for policy-makers.

[abtinf]

A plausible lower bound would be useful, but $4B is a joke. That’s less than the annual budget of single major university (Harvard is around ~$5-6B).

Gartner says the world spent $4.5T on IT in 2022. To pick some numbers out of thin air, let’s assume half of that is on software, and half of that is on new software (not maintenance). And the let’s assume that software is sold at ~20% net margin. And open source powers an enormous fraction of it at some level, but let’s be conservative and say it’s 10%. $4.5T * 0.5 * 0.5 * 0.8 * 0.1 = $90B per year just for the new stuff.

Recreating the existing stacks… if we multiple that number by 25 years, you are at over $2T to rebuild OSS in some kind of manhattan project.

But even that is a massive underestimate. For one, it would be competing with other development objectives—there aren’t millions of principle-level engineers just sitting idle. And more importantly, formally run projects have radically different levels of passion and “giving a shit” compared to how people often start OSS.

You simply couldn’t do it at all. It would be like asking “okay, but assuming we really had to replace all the metal with wood, what would it cost to launch a manned wooden rocket ship to the moon?”

[jvanderbot]

You are mis-reading the result. As quoted above:

> We then calculate the demand-side value based on a replacement value for each firm that uses the software and would need to build it internally if OSS did not exist. We estimate ... that the demand-side value is much larger at $8.8 trillion

But details like a 1000x change in estimate aside, saying it couldn't be done is not quantifiable. At least a dollar figure can be reasoned about.

[abtinf]

Saying it can’t be done is still an actionable guide to policy. If it can’t be done any other way, and it has massive benefit, then policymakers ought to be careful to avoid actions that harm it.

For example, tax law changes requiring multi-year depreciation of engineering labor probably have an extremely detrimental effect to small open source projects with commercial potential.

The policy effectively significantly raises working capital requirements for an early stage OSS company that might be focused on services revenue instead of licensing fees.

[jvanderbot]

We're missing the forest for the trees - the estimate was large ($5T), and the estimate is indeed a lower bound, and it seems like pretty damn important to save F/OSS.

[mitjam]

Spot on, and it forgets the creative aspect, it‘s like estimating the cost of reproducing all of the world‘s widely read literature. Who could recreate a Shakespeare from scatch, who a van Rossum?

[feoren]

"We estimate the supply-side value of Shakespeare's works by estimating the cost of paying an author to write the approximately 884,000 words in his collective works. We therefore calculate the value of Shakespeare to society at $320,000, or approximately the same as the value of 3 Tesla Cybertrucks."

-- MBAs, probably

[acc4everypici]

nobody because the times and places either of them lived in no longer exist. surely the places and the geographical locations and buildings are still there, but the people are all different, so it's not the same place

[klingoff]

That's important in literature in a way.. But does it matter to the economy if POSIX were created as it is or if some OS slush fund created a different computing model obsessed with some other primitve besides the file?

In our values a lot of literature is valuable because of how it came about. If Shakespeare never existed and someone wrote like him today we would just lock them up.

[doctorpangloss]

> Has any business school ever produced a paper worth a damn?

The research from Fader at Wharton is pretty significant.

[acc4everypici]

it's not about any of that "reasoning"... what matters it the conclusions: the results.

and even more than that, what matters is the capability of the paper to sway the opinion of real power.

our experience dealing with power may vary, in mine, power does not respond to "reasoning" nor any of that stuff.

nonetheless, I agree with your sentiment. why does science demand replication? IMO, a key underlying consequence is that ideas must be transferred, given away before they can be science.

the ideology of "real" human-centric science is equivalent to open source mindset. so then, my question is what to call all that research that happens, privately, in secret and under a lot of NDAs.... it is not science; that is product development.

[darby_nine]

Delving deeper

> To reproduce all widely-used OSS once (e.g., the idea of OSS still exists, but all current OSS is deleted and needs to be coded from scratch), using programmers at the average developer wage from India, it would require an investment of $1.22 billion. In contrast, if we use the average developer wage from the United States, then reproducing all widely-used OSS would require an investment of $6.22 billion. Using a pool of programmers from across the world, weighed based on the existing geographic contributions to OSS as discussed above, would lead to an investment somewhere in between the low and high-income country, $4.15 billion.

Note that they just assume that you can basically hire programmers to type that out and extrapolate from lines of code. So I'm guessing this is off by at least one order of magnitude.

Granted, I'm not sure if I have a better option, but I'd probably start with sampling OSS contributors to figure out how much time they actually devote to OSS.

Paper is here for the curious: https://www.hbs.edu/ris/Publication%20Files/24-038_51f8444f-...

[meiraleal]

That's still a terrible underestimate. Meta alone spends more than this in VR yearly with development and they are not recreating more software than the whole OSS every year.

[hyperpape]

The method that paper used was as useless as it could possibly be.

https://hachyderm.io/@hyperpape/111784908079127255

[whit537]

Agreed. When it first came out in January, I did a write-up and emailed Frank for comment. It wasn't until both my critique and his paper appeared together on HN for the first time that he responded ... with a total non-answer. :rolling_eyes:

https://openpath.chadwhitacre.com/2024/questioning-the-value...

https://news.ycombinator.com/item?id=39340146

https://news.ycombinator.com/item?id=39340277

[jchanimal]

Does this roughly equate to a 99.9% margin? Using comparable analysis if it was a company.

[Terr_]

> calculating the cost to recreate the most widely used OSS once

Let's not forget the new cost of taking those bajillion different implementations and making them compatible.