@Akos: Yes, the example now checks for null twice.
Mads Torgersen [MSFT]
I am the Program Manager for the C# language at Microsoft. I maintain the language specification and drive the design of new versions of C#. I also contribute to the design of VB.NET and TypeScript.
Hey, I fully understand the concern that new short hands can lead to more convoluted code. There are many short hands we could consider adding to C#. We are extremely careful to only add ones that we think lead to more clarity in common code.
With any new opportunity to compact code, there's going to be people eager to overuse it. It's a bit of an organizational challenge to establish what good code looks like, and how these new features can be used responsibly, in a way that fits the culture of the company.
That said, we don't feel we have a choice but to evolve the language to improve developers' productivity and better meet new challenges. We try to take a balanced approach, so that C# can keep growing for a long time without collapsing under its own weight. But grow it will.
Thanks for all the wonderful comments, both good and bad ones!
@FZ14: You wish for jQuery to be ported to TypeScript.
I just want to point out that you don't actually need to port existing libraries to TS in order to get a strongly typed experience consuming them. TS let's you write "declare files" that describe a typed view of existing code, so that you can get IntelliSense and type checking against them when you consume them from TS.
Our hope is that authors of JS libraries will also author .d.ts files for them. If you write your library in TypeScript, the TypeScript compiler can also generate a .d.ts file for it, along with the JS.