+972 52-548-6969
It will do what you want in version 3.0...
But feel free to start using it now. Adi's post is bringing back memories from conversion long gone:
I had practically this statement thrown at me about 8-10 months ago, talking about why the customer wanted to use DLinq instead of NHibernate.
Adi, my response to that is, "So?"
I can get a bottle of wine that will taste real good in 15 years, that doesn't mean that I need to start drinking it now. Sour grapes indeed.
Just to point out, another company did, Sun & Java. As for why I am using C#, have you looked at the alternatives? Before I did C# I was a C++ programmer. Can you imagine the stuff that I did with templates? I jumped into C# the moment I realize that I don't have to manage my own memory anymore. Hell, C# has one feature that is a killer. Stacktraces for exceptions. C++ has 0x324ABCD memory could not be "read".
I am not sure why, but I never got around to doing the other stuff (Java, Python, etc)...
Oh, and what is it with the babe?
Comments
What is with the babe... heh.. I was wondering that myself!
I find the "microsoft as a religion" thing bizzare... it really is a daft statement as well... why suffer "now" in the hope that the product your backing will eventually catch up to the competition - and in many cases it's not shown to be true, the recent .Net framework 3.0 is a good example of a suite of technologies which in many places replace existing implementations, and can't be seen as an upgrade path...
Update: After reading the comments to my post, it seems I didn't present my point as well as I thought I had, here is another try:
http://dotmad.blogspot.com/2007/03/not-religion-but-strategy-take-2.html
I'm not sure it's the biggest feature, but I definitely agree with you on the exception stack trace being quite valuable. I also love throwing exceptions with lots of information so that I can fire up the debugger less frequently.
Comment preview