The article claims 4 million gallons per ton to produce beef. Using a little imagery, I am picturing two steers (more than a ton of beef) swimming in a water tank of that size. Lincoln Nebraska's tank hold 4 million gallons. So what are these animals, aqua cows? They live in a Shamu sized aquarium? Maybe I'm just lucky because my cattle only each drink about 60 gallons a week. But you might say I didn't factor in the alfalfa. They don't really eat that much, two bales at most per week, each. So, two hundred pounds of feed per week, or about five tons per year. My uncle uses 1,000,000 gallons to water on his field of alfalfa, 15 acres, per year. Each acre produces about 6 tons per year so that million gallons goes to producing 90 tons of feed. That is enough to support 18 animals. 4 million gallons should support 72 animals or 36 ( a very modest figure) tons. That changes the assertion to 12,000 gallons per ton.

The truth is, alfalfa is used for milk production, not meat production. If you want to fatten up a cow, you feed them grains. You know, the carbohydrates that America uses as a primary source of their diet; which is why America is obese. The article talks about the cost of alfalfa driving up up the cost of beef. It is true that the Imperial Valley alfalfa farmers can ship their alfalfa to China on the empty cargo ships returning to China and make more money than they can shipping up to San Joaquin Valley where the dairies exist. The impact has been on milk prices and horse ranches. Alfalfa went from $9 for a 140 lb bale to $17 for a 100 lb bale. That upswing did nothing to meat prices. During this upswing, beef was incredibly cheap. I stuffed my freezer with $4 a pound rib eyes. There are other market forces that are now bringing beef prices up. The American herd is at a 60 year low. More people, less beef, more money.

I do believe the water figures given for vegetables to be fairly consistent. Most of that water doesn't go into producing the product, but instead evaporates off leaving the salts behind that ultimately destroys the land for farming. We have switched to hot house hydroponics. It uses a little as 1/20th the water as conventional farming. The reduction in pesticides is drastically reduced. The fish and crustaceans provide the nutrients that the plants need, and the plants and bacteria break down the fish wastes purifying the water. A hot house produces a tremendous amount of food.

If feels to me that the author as ideological agenda. The truth is, we are designed to eat meats, eggs and vegetables. Everything else, not so much. The American diet has caused an epidemic in obesity, diabetes and Alzheimer's. This is directly a result of what we eat today. You can read, "Grain Brain" for a neurosurgeons take on this subject.

Step 1: Receive Plate
Step 2: Microwave Plate
Step 3: Place non functional plate on car.
Step 4: Profit

That is exactly why costs are going up. A bank knows when they make the student loan, that it can't be dispensed in bankruptcy. It is a form of modern day slavery. Make those loans subject to bankruptcy and the prices will eventually drop. If not, when you get out of school, many places are happy to give you credit cards. Take them and use those little checks to pay down or pay off the student loans. Those do go away in bankruptcy.

Your ignorance is showing. C# rocks for doing the things that .Net is suited for. Quick enterprise applications where size of executable and ASP .Net, again on the enterprise network where bandwidth isn't a problem. Other than code metadata, I fail to see the congruence between .Net and Qt? Qt and Webkit are tightly integrated. You can accomplish in short order, applications that have the characteristics of a web application but also contains high performing cross platform native components. Hint, I've made use of this feature on a commercial project that you have probably used. Android and IOS are the present. Networked embedded devices are the future. IOS not likely to be the platform of choice due to licensing fees. Android is unlikely to be the choice either. Android runs on a stripped down version on Linux. So an embedded device developer will probably skip the Android middle man and go directly to Linux. No UI, no need for Android. UI? Then Qt's Designer is a WHOLE lot better and faster at designing UIs than Androids widget set. I think you are stuck in the present. So let us call a Troll a Troll.

Where's the like button? You of course expressed that which I meant to.

In what way is it MASSIVELY flawed? Drama major? It works on OSX as well. The announced framework edition is adding Android and IOS support. I have found problems in the framework. Guess what. I have have the source code, modify it and then rebuild it. That is a whole lot better than starting from scratch. Another poster here talks about getting threading right. QT does a pretty good job with threading. QObjects are thread affinity aware and will let you know if you are executing an object in a thread in which it was not created. Very often, I find the limitations of the framework are imposed by the underlying OS. Calling me green just means you live up to your user name.

I've been a QT developer for a number of years. Over the last few years, I've done some Linux embedded. A few months ago, I even built and ran a QT app on the Raspberry Pi. Everything worked except for animation. Nokia messed up by not staying the course. And now they announced they are happy being the challenger. Seriously? You were the world dominater several years ago. One thing not mentioned is the Blackberry port. The framework is well done and it just works.