HNHacker News
TopNewBestAskShowJobs

thelema314

104 karma · joined February 11, 2009

submissionscomments
thelema314··on Economics in One lesson - Henry Hazlitt
In both of your wealthy and thrifty baker examples, you seem to think that the $250 is stuck under his mattress, and needs to be pried out ASAP to do any good.

More likely: 1) it's being invested in some business activity, which loses that capital in order to pay for a broken window OR 2) he's earning interest on it, negating most of the time difference in your thrifty banker example

Lastly, even if it were under his mattress, putting that money back in circulation increases the amount of money in the market chasing goods, which increases everyone's prices by a small amount.

As to your serial killer counterexample, I think the correct analogy is "if it's harmful to the serial killer to die of a heart attack, it's equally harmful for the nation to die of heart attacks."

thelema314··on On Forking a FOSS project
Fork early, fork often. It's the GPL that legalizes merging, past that, the worst that happens is that someone wastes their time on code that doesn't get used. If it's the fork, tough cookies for them. If it's the "original author", they can choose whether and how to benefit from the code that has been written to extend their codebase.

If you're angry that he forked your code, fork his code back into your project. Or at least the parts of it that you want. The parts you don't, leave behind. Does it burn that you didn't get to order him around on how the project should have been improved? He doesn't need your permission, get over it.

thelema314··on Hacker style versus the Dijkstra style
This relates to the "version 2.0" dilemma. Version 1 of a program works well enough to make money, so that team gets to make a version 2. But they try to "redo it right" by making their product do everything conceivable (think emacs), but it's slow and buggy and in the practical ways, worse than 1. Version 3 (where they learn from version 2 how to make it elegant) doesn't get written because the team gets split up because v2 was such a failure. Another example of the v2 problem is Winamp.
← PreviousPage 2 of 2