It starts with Chris Sells, who says he wants “the power and performance of C++ and the simplicity of C#.” He links to a grumpy programmer blog that says lovely things about the new C++/CLI, including this in the first sentence:
C++ becomes a fully fledged, first class .NET language, throwing off the clumsy ‘managed extensions’ and gaining a full set of designers, code verification and mixed mode (managed and embedded) capability. It is thus the only .NET language that offers true backward compatibility with legacy code bases and delivers genuine performance benefits over C# or VB.NET.
He then goes on to say something that many people close to me say regularly: what the heck is C# for? I don't say this myself, I think lots of people love C# and more power to them, there's nothing wrong with it at all. It has a place. It's just not the only way to use semicolons and brace brackets while targeting the CLR, that's all.
The comments section of Chris' post is full of entries from people who don't know what C++/CLI is. I'm not being rude or dismissive, it's just that someone who complains about the double underscore keywords is complaining about the old syntax, and that is gone now. Read my lips: no more double underscores! Let's keep saying it till everybody hears it! ... er, sorry, got a little carried away there. If you haven't seen the new syntax, try Stan's “Hello, C++/CLI” column.
Next up is Sam, who confessed to me privately that he liked C++/CLI and has now come out on his blog: “I was expecting all sorts of horrors and errors but the code came out perfect in first try and naturally, the way C# flows for me.”
Craig Andera basically says “but people like C#” and you know? I'm not arguing with that. But why is it a win-lose game with C++ and C#? Why can't they both soar and do well?
A nice start to what will probably be a long hard week for me.