[dlu]

Angry much?

You lost me with the "code isn't a good that spoils" line. It is a great phrase, but perhaps you could re-explain?

[jsprogrammer]

A restaurant requires continuous inputs: fresh food, labor, electricity.

Code is a purely digital good. What was in the repo a few days ago could be released at no ongoing cost to FoundationDB/Apple and it will stay exactly how it was, forever.

[r00fus]

I disagree. Code gains technical debt over time, bugs are found, compatibility with other libraries and the OS fray, security vulnerabilities are exposed, and what were awesome features 6 months ago become commonplace or superseded by the new awesome.

Essentially, code starts to rot after a while.

[pc2g4d]

Its utility diminishes as the difference between its original environment and the current technical environment increases. However, given a replica of its original intended environment (e.g. an OS image in a VM) the code will run just as well as it always did.

So code does spoil. And it doesn't.