In his capacity as a senior leader of a major silicon valley company, he actively worked to limit people's employment opportunities. That tarnishes his record as a great leader.

More accurately: there is a higher concentration of overweight people at a store that caters to lower income brackets.

When machines do everything, people won't have to settle for cheap unhealthy foods.

Humans enjoy their bodies. We play sports because it's fun and feels good. We enjoy the burn of a good run. We like to look in the mirror and see something vaguely attractive. We like to fuck. And we want to fuck people we find attractive.

Wall-E got it totally wrong.

Until they show something to the public, I'll give them zero credence of having really advanced the state of the art.

  I know I'm stuck in the past, but that's what I want for my kids.  Flip open the laptop and boom, theres my programming environment, except now with easier graphics/sound APIs.  

C++ is a very abusable language. This is reflected both in its capabilities and in the ability to shoot yourself in the foot. These points are obviously well-covered in any C++ discussion.

Now, Alexandrescu brings a style of programming in which you exploit templates, sometimes macros, operator overloading, and everything else, in order to squeeze out more generality/reusability out of a piece of code, or simplify the coder-visible syntax of some construct.

We see that right here: the above comments show a few ways to run arbitrary code on a scope exit. Each of the examples above is perfectly easy to follow along. But then the YouTube video show's Alexandrescu's take, and it's a real brain-warper. He invokes a couple of levels of C++ trickery to get his effect. Now, his end result is wonderful... but it's also not easily understandable. If you write code in his style at your job, good luck to the person that takes over your code after you leave the project. They'll have a hell of a time.

IMHO a developer should always sacrifice syntactic sugar, with no performance penalty if done correctly, in exchange for more understandable code.

[1] The good ol' days.

Unfortunately the revolution seems slow to arrive. Since the official release of Rift --the grand moment we were all waiting for-- VR buzz seems to be going in the wrong direction. Yes it's early, but where's the flood of devs rushing to exploit this new tech? It's miniscule compared to mobile, e.g. when iOS and iPad were released.

I was hoping this article would hit on that main point, but it was only glossed over.

Are there any concrete proposals on the table? I don't recall seeing any, and it would be great to work from that and pick it apart. Otherwise, we're just arguing the opinion that they're useful, against the opinion that they'd soil the language.