On Mon, 2007-09-10 at 19:08 -0700, Richard Reynolds wrote: > I have my devils advocate hat on today just cause I do!!! > > On Mon, 10 Sep 2007, Paul G. Allen wrote: > > This afternoon my boss said we need a new test utility and he'd prefer > > it to be written using C# and .NET. Some of his reasons were as follows: > > > > 1. That we have to support Windows (mainly for customers) > .NET is a good choice for winhozed support > > > 2. As compared to Java, the GUIs work better and in general look better. > Lets face it! they DO! > > > 3. It's a common technology. > cant argue there, mostly because you didnt really define common, so I cant > argue. > > > 4. It seems to be the best technology set for Windows applications > > requiring a GUI. > again this is very true! > > > I prefer not to use C# and .NET at all. I don't like programming on > > Windows in the first place and have never used C# or .NET, but aside > > from that I prefer > I prefer not to have to rely on others to get there jobs done so I can do > mine, > but here I sit waiting for someone else .... > > > > open standards, > when the $ comes down on the current world "open standards" means nothing! > your > boss can have a superior looking product in less time/money then tuff stuff > to > java > > >non-restrictive (or less restrictive) licensing, > your reading the wrong side of the card. > > > > and technologies that allow the easiest porting from one > > platform to another. > which platform, if you have vb2.0 code you can port it into .NET if you have > .NET you can port it onto .... or you can use the sorry excuse for a java > interpritor that is available for windows in the entire time ive been looking > there are only 3 or 4 tools that were designed for java and work just as well > in > linux and windows mostly because they have been ported the right way, not > automatically or trusting some "magic interpretor" > > >I do believe in using the best tool for the job. > nah you believe in using tools you are acustom to. Or you would have known > .NET > was the best tool for the job... which is writing a tool for M$ winhozed > > > Portability doesn't seem to be a concern to anyone because "Everyone > > [customers] is using Windows and will be for some time." > Today I hate M$ winders but damn near everyone is using it!!! > > > > Long story short, he said if I can come up with valid reasons why we > > should use Java instead of C# and .NET, he'd reconsider his position. > the long story sounds like a LOT of fun!!! > > > > Why should a developer use Java instead of C# and .NET? > when there target is NOT winhozed! > > > Does .NET support GPIB or HPIB capable instrumentation? > YES > > > Are there licensing issues we should be concerned about if we write an > > application that we will > > then be giving or even selling to our customers? > > only a few, none of these are really avoided with your open standards, if you > steal code your not supposed to or if you steal the compiler, then there are > license issues. otherwise if you OWN the compiler and its not the student > version (that has a limited license) then there are no m$ license issues. > > > > TIA, > You asked for it > > > Richard Reynolds > [EMAIL PROTECTED] > I'm not really a software guy, but recently, I have to deal with C#, too.
My main grievance with it is that it behaves like a human manager: It assumes that the programmer is a total moron and makes high performance (i.e., unmanaged) stuff excruciatingly painful to write. One possible explanation why C# got introduced at the place I work at is that the manager of the software department found it in his best career interest to reduce everybody to the abysmally low standards of the least capable programmer, whose code he demanded to be "respected", thereby creating the artificial need for a lot of more management, and an artificial inflation of the headcount of his department. If your boss is a typical boss, then the unnecessary creation of the need for more of his management is NOT an argument against C#. -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
