pareklund pareklund

Niner since 2005


  • Anders Hejlsberg - Programming data in C# 3.0

    Coming from the Java world and just having dived into the world of .Net, I thought that Microsoft's view on this was more a pragmatic one, viewing Java's fascination with persistence layers as a mere academic exercise catering to unsatisfied egos and instead focusing on "getting the job done" without digging too deep into the Pandora┬┤s Box of object/relational mappings. Having said that, I don't say that the ideas of extending C# with object/relational mapping constructs are necessarily wrong. For example, having used the open source library/product/framework Hibernate for that in my latest project was clearly a positve experience. However, I wonder if putting the equivalent(?) into the language itself is the way to go. The KISS principle should be applicable here as well. In my humble, newbie view, C# is already balancing on the edge, with simplicity and elegance on one side (an improved Java) and with complexity and too many sharp (pun intended) edges (C++++) on the other. Adding to this the functionality of Comega might tip it off in the wrong direction and alienating developers as a result due to the resulting complexity. So, my question is really: Wouldn't it be enough to settle for an addition to the class libraries - say, like a .Net-ified Hibernate - instead of cramming even more expressiveness into an already very expressive core or is it really proven necessary to add native operators to achieve the desired results? Btw., are there alternative .Net libraries (open source or commercial) that provide object/relational persistence (corresponding to Java's Hibernate) already? Please, view my opinions as curiosity, not criticism. Wink Regards /Par Eklund --- Why doesn't newlines work for my post? --