You're absolutely right Rod,

But the thing is, and please take this lightly because I have'nt worked with .Net yet, after GUI there has to be some other kind of processing.

I guess that only a very small minority will use .Net to only build GUI without anything else.

What should be of high interest to the majority of developers? Data processing.

So if you have a tool (.net) that is only so so in GUI processing (WINFORMS) and so so in data processing, according to those complaining about .Net, then you can't have a development environment that is wonderfull.

Those topics need to be adressed and the proposed solutions should'nt be to say "It's not that bad".

When you have a new tool on a given market it should be at least as fast as what was there before.

I'll get back to VFP because that's what I (still) work with. Local data processing is very fast with it. Why I have'nt switched to .Net yet. Because I'm not ready to sacrifice that speed. To me businesswise I know that my customers won't be really thrilled if I tell them. "It's not as fast as the precedent version but I did it with .Net"

Perhaps the precedent argument is not right but with the replies you gave you kinda reinforce my "Feeling" that .Net is not there yet (according to local data processing). To me it looks like you give too much importance to GUI. Is it because local data processing is that bad?

Sadly I don't have much to argue with you. I'm just saying this based on my feelings after what happened on this thread.


>John,
> You sound so much like JVP. You can see my point. UI is UI is UI. The database issue is a red hering. You know it and I know it.
>
>You ignore my point a UI with lots of controls is a UI with lots of controls. It does not matter whether or not it is a graphics app, database app, game or whatever. UI response is equivalent across many types of apps.
>
>I know you are smarter than that and can see my POV. I'm done with this now.
>
>
>
>Rodman