Lets suppose
-
Ennis Ray Lynch, Jr. wrote:
Believe it or not there are some things you can do in Java that you cannot do in .NET.
With all due respect: Isn't it just possible that you should be saying that there are things you know how to do in Java than you don't know how to do in .NET?
Jon Smith & Wesson: The original point and click interface
I don't know how to make my .NET application run on Solaris, Macinitosh, Linux, Win95, Win98, Win2000, WinXP, and WinVista all at the same time without writing a web-based system that won' work in this case.
Need a C# Consultant? I'm available.
Happiness in intelligent people is the rarest thing I know. -- Ernest Hemingway -
I don't know how to make my .NET application run on Solaris, Macinitosh, Linux, Win95, Win98, Win2000, WinXP, and WinVista all at the same time without writing a web-based system that won' work in this case.
Need a C# Consultant? I'm available.
Happiness in intelligent people is the rarest thing I know. -- Ernest HemingwayEnnis Ray Lynch, Jr. wrote:
I don't know how to make my .NET application run on Solaris, Macinitosh, Linux, Win95, Win98, Win2000, WinXP, and WinVista all at the same time without writing a web-based system that won' work in this case.
Good answer. :-D
Jon Smith & Wesson: The original point and click interface
-
I don't know how to make my .NET application run on Solaris, Macinitosh, Linux, Win95, Win98, Win2000, WinXP, and WinVista all at the same time without writing a web-based system that won' work in this case.
Need a C# Consultant? I'm available.
Happiness in intelligent people is the rarest thing I know. -- Ernest HemingwayEnnis Ray Lynch, Jr. wrote:
I don't know how to make my .NET application run on Solaris, Macinitosh, Linux, Win95, Win98, Win2000, WinXP, and WinVista all at the same time without writing a web-based system that won' work in this case.
You have a good point there :D I don't think I would bank a software project on something like mono. At the same time I'm guessing you'll have plenty of issues getting a "GUI" based java application to run nicely on all those system. It always depends on the app of course.
Todd Smith
-
I'm confused - how would I grow broke by getting something running to show the customer early? Call it semi-RAD or agile, whatever, but requirements have always been the bugaboo in s/w development. Wait, is "show the customer working code" the part you object too? I'd change that to working product. No customer needs to see source.
Charlie Gilley Will program for food... Hurtling toward a government of the stupid, by the stupid, for the stupid we go. —Michelle Malkin
charlieg wrote:
No customer needs to see source.
True except that the customer has to foot the support bill. If this is not part of the negotiation the customer has no idea what is in stall. Support is a larger cost than the development cost and if it is an obscure technology then support resources become an issue. Actually I don't argue with the prototyping, I would often do this to sell a solution. My objection is your reducing the importance of the technology flavour, in my experience it was often a deal breaker. While small business usually does not care, medium and corporates certainly will.
Never underestimate the power of human stupidity RAH