Replies

We was the greater "we" as in "participants of the thread". And no I was desperately hoping to avoid an arguement with you because you argue like a 5 year old conspiracy nut. If you'll recall months ago I requested that you never post to me again. Since then I haven't posted to you, nor have I posted on threads you were on, I even stopped posting on threads you came to after I got there. Until monday morning when I post to Jeeves, just dipped the toe in the water for a moment, had no intention of it turning into something big. Then you posted at me.

No MS only people don't like you because you insult them. None of us care what you use. The probem comes in when you start telling us we're fools for not doing what you do and are a liability to our company.

But of course this is the classic example of what's worng with you. You can't concede any point no matter how small. There are 3 sane reactions to being told you insulted someone. The person who did it unintentionally will apologize and possibly ask for clarification on how they were in sulting. The person who did it on purpose will either blow it off or reply with something even more insulting. You will argue the point for two days inventing wild oxymoronic phrases like "politely suggesting they wasted their boss' time and money". Why? Because you're not sane. It's anathema to the very structure of your personality to ever give an inch and must change others. Anyone that is insulted when you question their decision is WRONG, anyone that doesn't use Java after all the great things you've said about it is WRONG anyone that use MS products is WRONG anyone that puts for evidence that you're feces actually does stink is WRONG; and they all must be beaten into submission.

As for my opinion of .Net, which i don't use but I've spent long enough on MS's bleeding edge I've got a pretty good feel for their first rev is simple and I've posted it on this thread already, but you didn't want to listen and won't want to now. It's new so it's got lumps. Those lumps by no means keep it from being ready for primetime, which is proven by the number of organizations that are using it in primetime right now, it just means they need to factor in some slightly higher development costs getting it to primetime because they're going to have to navigate through the lumps.

Now for the new news that I hadn't put elsewhere. There is one really good reason to use it inspite of the lumps. It's the same reason there is to be an MS shop: interoperability. Nothing talks to a MS application like another MS application. As a matter of fact no app talks to another app like two (or more) MS apps. MS apps work and play well together. You want to get the most out of your MS SQL backend, write the frontend in something from MS. I can and have taken data from MS SQL with Access, massaged it, dumped into Excel, added a graph, inserted the entire spreadsheet into a Word doc and e-mailed that puppy out of Outlook through an Exchange server. And it's easy too. Just a handful of mouse clicks and you're moving data through 6 different apps on three different computers, and most people probably don't even realize they're doing that kind of stuff, that's how smooth it is. And the scary news is that except for the e-mail part you've been able to do that since the 3.x days (though it was a real bitch to code, man OLE sucked... until you got it working). MS haters call it illegal product tieing. Users call it damn convenient. And I have absolutely no doubt that .Net continues the tradition of being better at communicating with other MS products (or other things created with MS products) than anything MS doesn't make. It's what they're good at, it's the reason MS is able to sell the MS only model to so many places. Interoperability rocks, and nothing MS doesn't make can hold a candle to them in this area. Even when MS products suck (which happens, no denying that, though not nearly as often as the basher say, and less often every day) they still talk to each other smoothly.