In my job capacity, I often have to create custom search applications. As a whole of the project, this is given very little time and money. What is given time and money are incredibly complex interfaces with lots of options. I have to assume this is because a search interface often has one (or a small number) of inputs (therefore is easy) while an interface dealing with categorization on multiple facets, tags, etc. has lots of complexity (therefore being hard).
Simplicity is hard to charge for because it looks easy. When something looks easy, we don't value it highly. Basically, we understand the work that went into cludgy, complex interfaces because we see it. We* don't understand the complexity of something simple like Google.
*The "we" is meant to be the public, not really people on news.yc.
I think it takes a lot of effort and courage from the designer to decide some - and hopefully the right - things for the user knowing that the risk is to provide a product that might not meet every user's needs. The timid and lazy will push the decision and effort off on the user.
The answer to your second and third questions are both "yes."
A lot of developers take pride in building complex software. Bad developers do it because they just shut up and code, and turn software that should be simple into a giant pile of fragile spaghetti code.
That leads to a high maintenance overhead, so adding features becomes a lot more labor intensive than it would be with a good piece of software... hence higher cost.