Yesterday I sat through Intel's tutorial on Intel's Threading Building Blocks at OSCON.

The library looks pretty interesting, and I've been looking at the
interface and white papers to see how it was written.

Good white paper:
http://cache-www.intel.com/cd/00/00/30/11/301132_301132.pdf

The part I don't get?

Its C++.

They missed the point. Most of open source is in C. If you want
ubiquity, you write in C. You can wrap C into C++.

Or Perl, Python... but C++? Pain in the ass.

If I write something for just myself I'll use C++, but if I want
ubiquity? Its going to be C.

What would have been an even bigger leap in thought for this release?
Find a way to …