Heck no. By then, the Internet as we know it will no longer exist, Lenovo will have been out of business for decades, and the IPv22 networks that connect the nanobrains that governments will embed inside our mitochondria, at birth, will no longer understand how to process or route IPv[46] packets.

It was used for a time in the U.S. as well (60s and early 70s), with disastrous results.

I'll agree on points 1 and 3. However, I would not consider code to be "clean" until it is readily understandable by any average programmer with a basic level of domain knowledge.

This is well understood, and means that testosterone therapy is contraindicated in people with, predisposed to, or having a family history of these problems. That would include me. It also means it may be risky for others. I am considering it anyway, for the simple reason that I'd rather be maximally healthy for 20 more years than to live 40 in my current condition, which is influenced by low testosterone (it is not absurdly low, just a little, but still affects my life in countless ways, nearly all of them negative).

I agree, but a man will benefit from those activities even more if his T starts out being near, or perhaps even slighly above, normal levels, with "normal" being defined not as the average today, which we know is much lower than in the past for various reasons, but the average from 30 years ago. I am not sure this is a bad thing as long as there is competent medical supervision. It's not for everyone; as others have pointed out, it can worsen heart problems, hypertension, aggression, etc. especially if done to excess. But many Americans are low due to medications, chemicals, age, etc., in addition to still-as-yet-unproven reasons. Proper diet, exercise, *and* supplementation may turn out to be the right solution for many people.

Python has the huge advantage of being fairly easily readable, if you can get past the whitespace-as-syntax. Readability is HUGELY important in the real world, because most code is read far more often than it is written.

I can do C, Java, Python, and .NET (C#) just fine. I can also muddle my way through C++ when I must. However, I'm nowhere near smart enough to do C++ well. I can't memorize the many edge and corner cases in the language definition itself, never mind the specific compiler implementations. I can't easily follow C++ code from people whose styles are significantly different than my own. There is a HUGE need for a systems programming language that is close to the metal, allows for higher-level abstractions than C, but is safer than C++, especially for mere mortals such as myself. I'm not familiar enough with D, Go, or any of the other contenders to know whether any of these is a good candidate to fill the niche created by the insane complexity of real-world C++. (Yes, I know that modern C++ is a much saner and cleaner language, but all of the legacy cruft is still there, and therefore must be understood to do C++ development in a team.) I predict that anything that is even close to being an acceptable substitute will eventually displace it.

I was trying to be kind. I'm actually quite impressed with some of the work Microsoft has been doing, including open-sourcing large parts of .NET, and evolving C#, which was already a great OOPL, into a truly multiparadigm language. I'm not terribly unhappy with some of the othe products that have been mentioned, and I'm not aware of anything else quite like Visual Studio. I don't hate Microsoft because it is Microsoft; I don't hate it at all. I do think that some of its past and present business practices have harmed the industry including Microsoft itself, and that they need a strong, consistent vision if they wish to survive the transition from a desktop- to a mobile-centric world. A UI framework that was truly best-of-breed, open-sourced and yet largely controlled and stewarded by Microsoft, could have been a great opportunity for Microsoft to establish and maintain a foothold in that world, and, over time, even to help bring Apple and Google down a notch, by helping promote a standard way to build UIs rather than proprietary iOS or Android (or WinRT) native apps. Now, my prediction is that evolution is going to happen anyway, but it will be focused around the HTML5 stack rather than anything from Microsoft.

By some measures of success, sure. But my understanding is that Microsoft makes minimal money on most of these products, and even loses money on some of them. Windows and Office have always been the cash cows.

I was surprised that the WPF issue has not been discussed more. Aside from C#, which is a sweet little language in most respects, and still ahead of Java IMO, WPF is the other fairly unique thing that .NET Microsoft brings to the table. It has no real parallel for the rich- or smart-client use case. (Mozilla's XUL is perhaps the most directly comparable FOSS technology.) And it is NOT being open-sourced. In fact, instead of throwing its weight behind a single WPF / XAML implementation, Microsoft allowed it to fragment between Silverlight (deprecated), WPF (supported only in the most lackluster fashion), and the client component of WinRT (Windows 8 only). This may in fact prove to be the opening needed for the modern HTML5 stack to become the preferred rich- and smart-client deployment technology even for desktop and laptop form factors. In that case it would also rapidly eat away at the very last piece of the technology business that Microsoft dominates.

OK, yes, but don't worry. It will be split into 4,212 different assemblies (although each will depend on all of the others). :)

But then Big Pharma doesn't profit. Therefore, it won't happen. A better idea IMO: dose *yourself* with appropriate amounts of these nutrients (I'd say much more than the current RDA, which is useless, but still less than you suggested, only because that much C would be prohibitively expensive and that much D could be toxic over long periods of time; 1-5g of C and 4800IU of D should suffice in a person not already sick). On top of a proper diet including lots of green leafy veggies, fresh fruits, and as little other sugar or high-glycemic carbs as possible. And start now. Odds are you will be much more resistant to any viral infection, and will defeat it much more easily should it happen anyway.

Don't hold back dude. Tell us how you really feel.

For most people it probably will. I was not so fortunate, at least not yet. My research leads me to believe that in as extreme a case as mine, there is a lot of arterial damage already, and BP won't come down much until that is reversed. I will say that my cardio endurance has improved a great deal . . . I went from not being able to walk a mile without pain, to being able to run 4, albeit at a fairly gentle pace (13-15 minute miles), in just under 2 months, although since that time I keep injuring my calf, rendering me unable to run although I still walk and bike an hour a day when possible. So my heart, liver, and kidneys are probably still serviceable, but I'll need time for the arteries to become more flexible. Interval training is said to be better for this purpose than pure cardio, and I'm looking into how I can do some without continually re-injuring my legs.

HFCS is indeed broken down more rapidly which likely accounts for much of the difference, for the same reasons that high-glycemic carbs cause more damage than the same amount of low-glycemic carbs. Sugars follow different metabolic pathways when too much are consumed in too short a period of time. But, in addition, there are several other concerns regarding HFCS: (a) It is often contaminated with heavy metals, which damage the body in similar ways as fructose itself (and more - they are generally neurotoxic as well). (b) It contains large traces of the enxymes used in its manufacture, which have the nice effect of breaking down other carbs into sugars early in the digestive process. (c) It does not need to be broken down into fructose and glucose, as does sucrose, which is most of why it is absorbed more rapidly. And (d) because it is cheaper it is used in much greater quantities than sugar.