(I'm not sure what the ratio is now.)
The second paragraph of the "Incidence and Importance" section of the relevant Wikipedia article (Iatrogenesis) lists some interesting references and numbers...
People think I'm crazy having only gone to the doctor a few times in the past decade and a half, and I see people in the comments here looking askance at herbalism and other folk healing traditions, but I feel much safer relying on these for everyday problems.
Obviously, garam masala can't perform heart surgery and lovage can't treat epilepsy, and I'm not saying to forgo science in favor of tradition, in fact it would be great if there were more studies on the properties of herbs and their essential oils, etc.
The fact is that there are safer alternatives to running to the doctor every time something seems slightly amiss with one's health!
he citizen that has a right to vote, is infinitely more powerful
That is, unless you are convicted of a felony.
Voting is a way to reach consensus between those who agree to heed its outcome. Corporations are at the mercy of the government less and less. Government is at the mercy of the corporations more and more. Let us also note that what is true in the US is not true or not as true in some other countries. I mean, most of the world's top economies are corporations rather than countries.
Don't forget that things change. Because the majority of those in power today are pampered, lazy pigs doesn't mean that tomorrow they won't be pampered pigs with intentions of institutionalizing corporate feudalism for the next 300 years.
These guys would write foreach loops that would suck most of the database into RAM.
NHibernate provides modular caching, so this is what you want. Generally, the data in the database is used by the application, so the more that is in memory the better.
I found that it just makes data access more complicated
It is perhaps the only library that allows true OO for database driven apps in
To make matters worse, when I used NHibernate, there was a bug in runtime code generation, which was very hard to track down and impossible to fix.
I sort of doubt this. Can you provide a ticket number for this bug?
Stick with a simple ADO -> Object mapper and write queries as-needed.
Perhaps if you are writing one-off homepages and photo albums and can't be bothered to learn how to write decent programs (or maybe you are a VB programmer anyway).
Don't rely on a more complicated library to handle things like transactions
As the author of several 10,000 to 100,000 user web applications, I can tell you that NHibernate's transactions and the lock construct from C# are amazing. Furthermore lazy loading and relationship mapping work great in NHibernate... It is very easy to specify when you want a relationship to be lazily loaded and when not, a simple attribute value needs to change.
Be very careful introducing relationships into the business objects, especially automatically-populated ones
(This is what lazy loading is for and it is very easy to set it on or off.)
As a final thought, I would ask why to use NOSQL databases with C# when you can use NHibernate and memcached to persist objects without a need for another data layer? There are plenty of valid reasons either way. And I'm sorry to take the piss out of you, but you don't know what you are talking about.
In any formula, constants (especially those obtained from handbooks) are to be treated as variables.