Hello Kevin

Well... my company has done quite a lot of work in dotNET- including HL7 interfaces, port captures, database stuff. Some of it works. Some it it works really well. Some of it is horrible. Some of it is so horrible that you'd have to ask "why?!"

I must say, when I see people (elsewhere) boasting that they can use dotNET remoting to help overcome the performance issues of bring large data across the wire - "yes, you too can write your own data chunking transfer mechanism" - something handled cleanly by indexed lookups ever since I started with FP2 - then I just *know* that dotNET has some maturing to do. For those who have a productive job and some security, there really is no "rush" or need for immediate intense navel-gazing. Especially when even the most fierce proponents don't quite seem be earning a living from real live customers rather than other developers yet ;-)

I guess I could "boast" that I am qualified to comment - I was one of the ones who moved everything across to Java in the early days... who could have dreamed of the difficulties that would follow... versions of internet explorer that crashed the JIT... tool companies collapsing... oh, except for JVP, that is, because he says he could "smell" the problems coming. ;-) Still, I wouldn't wish that on anybody.

Overall: I think this is a smart community. People here *are* watching and looking. Seems odd that people who would *never* berate, scold and lecture others in real life, seem to think it is a virtue to come here and do just that.

Regards

j.R