>Nope, It is not. If you don't have real life experience in .NET it does not mean you are not qualified to make an informed statement. See the lists below. I do read a lot of .NET stuff and in my discussion with .NET guys I started studying ADO.NET into detail. So I know damn well where the ADO.NET falls short. I do read articles, magazines, talk to people with first hand experience and read numerous posts on this subject posted by other members I respect here on the forum. But if you're not willing to believe I can make valid statments on the issue then go and talk to for example to John Ryan who seems to have more first hand experience on the issue than the load crowed and has worked with .NET form about the day it was released. Listen to Rick Strahl what he has to say on the issue. Don't forget to ask Cetin B on his opinion.

I never said you couldn't make an infomed statement. I said you state opinions as facts.

>You'll get a total different picture than the 'magical silver bullet' impression you get from the load crowed.

I have not formulated an opinion on .NET yet. Made a point of essentially saying that already.

>Jay, I don't think you understand the way software development works. Most architects never have done any practical work on the buildings they design. They don't select materials based on the practical experience they've got. Instead they rely on the published articles, imperical numbers and facts, but foremost on their theoretical knowledge and creativity and intuition.

When were we ever discussing design? Can the archetect build the house? It's likely that every person in these forums are developers, not just designers. I don't believe I've ever met just a designer. Project Managers and QA specialists, but not someone who preaches the facts of development who has never developed.

>I simply won't develop .NET applications until it is time to do so from a business point of view. In order to know if and when i've got to move, I'd better be well informed and have analyzed what the advantages and disadvantages are. So I've done that in the past, I'm contineuing to do that in the future.

So, if you are not already well informed, why would you state "facts" to those who are in the same place as you?

>Basically what you're saying here is that you should just blindly step onto the .NET boat and you are only able to judge if that was a wise move when you've completed your first major application. Won't you agree that is a little too late ?? From a business point of view that is the biggest blunder you could make (learn the lesson of those JAVA shops).

You will not find anywhere where I have said that. My issue is with your presentation of the "facts." I am still undecided what direction I will go and would like to see actual comparisons rather than pronouncements.

>Of course you could rely on a few big mouths promissing you the 'silver bullet' and ignoring the warnings you get from others, but that also is a perfect way to get bankrupt if things turn out differently.

And that's exactly why I like to see what people in the real world are doing with different languages. Not theorists.

>No, better is to analyze the issue yourself, gather the info you need to make a decision, then you've got only yourself to blame when you made the wrong decision when thing turn out wrong. Note that I'm in this stage. And I'm not ashamed to speak out loud about the disadvantages I find, because I know the load crowed won't come up with those until they are faced with it.

Exactly. Give me comparisons and practical knowledge and I'll be one of the first to get in line to listen.

>Do you really think that any IT management is going to gather all practical experience before deciding which development platform is suitable for implementing a strategic software solution? do you ???? Do you really think that the programmers are going to decide which development platform is going to be used ??

You must work for one amazing company. Any place I have worked the experience has played a large part in management making decisions. In fact, most most be given compelling reasons, and see real world cases, before they will change their development language. But if yours simply relies on unsubstantiated concepts, then you are in one interesting place.

>So in your opinion how is the IT management going to make an informed decision ???

See previous inline comment.