Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

An analogy to making a physical tool doesn’t really work because we have to basically describe what software is in terms of exceptions to the analogy.

If I had a ratchet that, every time I turned it, I had to pay $.1, but I’d gotten it for free, but it was basically free to replicate, but the person who designed it did have to spend some significant work on R&D for the thing… I have no idea how I’d price that or how I’d feel.



oh you really butchered that metaphor.

The ratchet isn't what's getting paid in the metaphor, it's the person turning it.

There's always a time-sink cost to a public project.

Anyway, there's definitely a public good argument to turn certain software projects into utilities.


I don’t think that’s what they were going for. They said “ I'd be pissed if I had to pay $0.10 every time I turned a rachet” so the person turning the ratchet is the one paying. Who they pay to is unknown.


ok, but the ratchet isn't what's being paid. It's the labor. The ratchet is irrevelent. It's the time it takes. And it's the POV.


It isn’t clear if you are trying to improve the original poster’s analogy, come up with your own, or change something about mine.

But, regardless, my main point was that describing the software in terms of a ratchet is not very helpful because hardware and software are different types of things.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: