
Theoretically, on a completely empty highway I can achieve speeds in excess of 200mph in a sufficiently powerful car. In practice, most highways will be congested, police officers will be present, the weather may be bad, etc., and I will never be able to go above an average of 60 (in rush hours of many cities, even less). To that effect my compact car is all I really need, and I am more interested in routes to and from work that will avoid congested areas instead of freeways that offer a theoretically higher speed.
Likewise, this article isn't about raw speed, it's about what is practically possible. This is an excellent guide for those interested in data plans.
The original poster's sentence isn't a dichotomy. There's no implicit statement that working in any of the jobs listed are the only options; the poster is simply expressing a personal opinion via a comparison.
What bothers me is the sound effect...
You've written quite a bit here about optimization. I certainly won't dispute that there's room for improvement, but I think you're missing something crucial. Minecraft has, and perhaps never will be, a game that relies on graphics, high-performance architecture, or even a reasonable FPS. If architecture bothers you that much, there's no shortage of games out there built on very robust engines such as the UDK. Instead, Notch has wisely chosen to focus on doing his best to refine the actual gameplay. The end result is a literally endless, randomly generated world that for some reason people are willing to pay good money to play in.
As for his choice of rendering tech, it's noteworthy to point out OpenGL 1.1 is one of the few graphics choices left that will practically run on anything calling itself a GPU.
"Well hello there Charlie Brown, you blockhead." -- Lucy Van Pelt