Anders Hejlsberg – Programming data in C# 3.0 #

Dan pointed me to a new video on Channel9 about some of the things we’re talking about for C# 3.0

Comments (6)

  1. John Rusk says:

    I read some of the links that readers have posted in response to the video. At first glance, the COmega approach seems to require developers to learn a lot of new concepts. I’m not 100% sure that I like that, I guess it depends on how well you guys implement your plans, while still retaining the emphasis on simplicity that you’ve expressed so well in C# 1.0 and 2.0.

    Personally, I’d be happy with features that simply let me express criteria for my database queries in C# syntax. This could apply to both SQL based queries or some kind of object-relational mapping.

    E.g. rather than writing something like this

    cmd.CommandText = …. + "WHERE table.field = ‘" + someString + "’ AND table.field2 = " + someInteger.ToString() ;

    I’d like to be able to write

    newCmd.Command.Where = table.field == someString & table.field2 == someInteger;

    This is a simple thing, relatively easily achieved with operator overloading (I posted details in your thread for C# 3.0 suggestions, even tho that’s not quite the right place). This seems to me like a good "win", and easier to understand than actual changes to the language.

    PS. If anyone’s interested in some basic code to demonstrate the above, email me thru my web site.

  2. Shawn B. says:

    While I don’t mind hearing about new stuff, for the most part, all we ever hear about is what we can do next year when 2.0 is released and most publications and announcements scarcely focus anymore on what you can do today. Now, we starting to hear about 3.0 and 2.0 isn’t even nearing completion yet. It is insulting… it gives off the impression that Microsoft doesn’t believe in its current product. If they don’t, then why should we?

    Just my 2 cents.

    On the other flip of the coin, the new features sound interesting but I’d rather not know about them until it nears time to release it… not two years before it is released even into beta, but when it becomes a possibility to leverage it. I fear that we’ll only hear about 3.0 once 2.0 is out the door and every publication will focus on that and never truly give credit to what can be done today. I’ll have to read the archives of all the articles that were put out during the 2.0 beta/pre-beta to keep learn anything.



  3. John Rusk says:


    I think, and hope, that Eric’s postings about version 3 are more about asking us for feedback than telling us what will be in 3.0. The content of 3.0 is not decided yet, and I think its great that Eric tries to get feedback from the community.

  4. Daniel MD says:

    Microsoft people these days, just try to solve everything with new programming languages, or exotic syntaxes, etc… Never really thinking deep enough about what they are doing, adding 10 new features per year on a language should not be the goal.

    addressing the issues that developers are having problems with, thinking ahead of the curve predicting new problems and spending more time planning than implementing, is what I want from a language vendor, not a new version every 12 months, with more “tricks” to be learned, that wore not properly addressed in previous versions.

    Most problems people are facing today will not be solved by new languages nor mixing syntaxes, and I must say that the idea of C# 3.0 being some sort of super-glue (OO/SQL) is very appealing… initially, but if you think about it for a little wile, that means new and esoteric syntax to be learned, the first version will probably be very limited.

    It will be very messy, and of course a new version of SQL server will have to be adopted, a new standard will have to be approved so that the other SQL database vendors can be compatible, etc… It will be a very big mess and you know it.

    C# 3.0 Super-Glue, has a higher probability of being a problem, not a solution, (added complexity for sure, ah oh COM/COM+ all over again).

    Instead you should improve on proven solutions (TOOLS) Visual FoxPro, is a great tool, developing the proper tools in my opinion is the way MS, SUN, etc… Should be going, pass the Imperative, go Declarative, but use the proper tools to make declarative a proper developer ecosystem.

    IMHO new an innovative, better tools is the way to go.

    Oh boy, I let myself get a little carried away, sorry for the long post. But I believe those building new tools that make the developer life easier, and enable him to be more productive, more creative, and simply more fun will be the winners.

  5. jake ham says:

    Daniel, I think that you are way off on your assessment. The C# team has done nothing but create a language that tackles the problems that developers face today. I think you really don’t have a good understanding of what C# and the .NET platform stand for. Start here, and then start looking on google.