i wrote a few comments about free rider problems:

the first thing to keep in mind about free rider problems is that in many cases someone pays. if Europe is really free-riding on Iran defense, then despite the free rider problem the US *did* pay for it. this may violate someone's sense of fairness. however, if i want to buy something, and it happens to benefit others, and i know they won't consent to pay for it, and i still want to buy it at full price, that is perfectly reasonable.

the second thing to keep in mind is that what projects should be done is a tricky question. there are more available projects than their is wealth to complete them and we need to try to choose the best ones. so if a project doesn't get completed for whatever reason (such as people who stand to benefit refusing to pay for it), even if the project seems valuable, that does not prove anything has gone wrong.

the general solution to deciding which projects should be done is individualism. people complete whatever projects they want to using their own resources and free trade. this works well because it lets people put their knowledge to use if they believe it's important without having to convince the world, and the people who are more successful at their projects end up wealthier and thus more able to do more projects.

the general solution to free rider problems, and to selling things to people in general, is to use creativity to persuade people to trade with you.

some people believe the government is the solution to free rider problems. they believe that by applying force to make the project be completed, they can improve the situation, by making good things be done that wouldn't have been done otherwise. however, there is no guarantee the government will sponsor the right projects. governments have no special knowledge about which projects should be completed. governments also have problems with accountability and efficiency.

a critical issue besides which projects should be complete is: how should they be funded? when a government intervenes by force and takes $100 from all the farmers to build a dam, even if the dam ought to be built, this still may be the wrong way to build it and a bad deed. funding projects in good ways requires creativity.

the only way that force could be necessary, in principle, to make the right thing happen is if there were right things such that they should be done despite their being no possible way that anyone, or any group of people, would freely pay for it with his/their own wealth. if that's the case, in what sense is it really the right thing to be done?

Here I stand; I can do no other - Martin Luther

Syntax is supposed to be a win. It's supposed to be convenient, readable, shorter.

But Lisp -- the language where you write your code in trees without syntax -- is known for being very succinct.

So I see two possibilities:

1) Most syntax isn't actually a great idea

2) Other languages are so handicapped by lacking features found in Lisp that it more than makes up for syntax advantages (and libraries, and all Lisp's other deficiencies)

I'm leaning towards (2), but I suspect a fair amount of syntax is not helpful and some is bad.

If your child doesn't want to look for solutions, this does not mean your child doesn't want to solve problems. Really. Your child isn't insane and *would* prefer if things were better. What's going on is that previous time spent "problem solving" was unpleasant and was itself a problem. Perhaps because it seemed boring and fruitless. Or because it involved the child being pressured to make compromises or sacrifices (same thing), or lectured, or asked questions he didn't want to answer. Or maybe "problem solving" previously interrupted other things like video games.

True morality isn't unpleasant or burdensome. Moral knowledge is knowledge of how to make choices. It's a tool that has information about how to get what we want, and what we should want. It's not arbitrary or artificially limiting. If something is a bad idea, true moral knowledge on the subject will include reasons why it's a bad idea and explanations of what will actually work well. And they will be persuasive. If they aren't persuasive, that indicates a *lack of* moral knowledge. If the "moral" alternative proposed doesn't sound nice, that indicates a *lack of* moral knowledge (either the proposal is wrong, or the explanation for it isn't good enough).

link

girl: i love you
boy: i'm not sure if i love you
girl: well, how will you find out?
boy: dunno
girl: will you know soon?
boy: i doubt it
girl: this is important!
boy: why?
girl: i don't love you anymore

i told Ann i'd hack jack's computer and knock him offline. i asked jack to logoff AIM for 20 sec. so jack logs off and i told Ann i did it. the most amusing thing went wrong: before he left, jack told Ann "Elliot is asking me to logoff for 20 sec. brb"

From the ruby-talk mailing list. Quoting removed, I think it's readable out of context.


How can a (coding) convention be *wrong*, instead of just less useful, less practical?

The same argument applies to other conventions. Why is Sati *wrong*, instead of just a less useful, less pleasant way to live?

Ideas have broad consequences that can't be arbitrarily restricted: they reach out to other fields. The full answer to the Sati case should include whether anything is wrong at all, and whether practical considerations have moral consequences. Those issues are important to the question about coding.

We can even take a dialog about Sati, and then use some of the ideas to argue about coding. Most of them will work just as well about either topic.

Jim: "Sure, Sati sounds horrible to us, but they are accustomed to it, and would be unhappy to live another way. It has practical consequences, like reducing how many women are available to knit, but wealth is only a convenience."Chloe: "Medical textbooks are a kind of wealth, and medicine matters. With less knitting, they won't be able to buy as high quality medical books."

So, back to coding. This medical textbook argument will work great. Some programmers write tools for doing page layouts, and for making diagrams. Those tools help us make better medical textbooks. The more convenient and practical the coding conventions of the programmers, the sooner we will have higher quality medical textbooks.

The idea that medical textbook production is a *practical* issue with *moral* consequences can be transplanted just fine between the two cases: it has reach.

This isn't conclusive, of course. Maybe you don't see the moral value in medicine. But I think it's getting somewhere, to tie those things together. Most of us are probably persuaded by now. And if we were to continue on, about Sati, or coding conventions, we'd continue on in exactly the same way -- discussing medicine -- because it's all tied to the same issue now.