.NET or open source

[Dab]

Can anyone point me in the right direction here? One of our clients is tossing up which way to go; either .NET or open source. They have some software written in visual basics that now needs to be rewritten in order to become web-enabled. It appears that they are willing to rewrite the whole programme for the web, so, it's not really an issue. But I would like to convince them to go Unix way, of course! Any suggestions of places I could direct them for a good analysis of the issues?

[Spathiphyllum]

This sounds like a Montagues vs Capulets or Mac vs PC question... pros and cons either way with lots of emotion from the ideologues.

Just for grins, I vote "open source" if the time frame is long term. Otherwise, and since most of the work has already been done, continue with the proprietary MS solution. This is back of the napkin generalization but I've found infinitely more solutions when searching in the arena of open source. Clearly, the skill set of the support crew should have some say to the final path, but I think you would find the community support as well as flexible options better with non-proprietary solutions. Plus, you may not need to pay a premium for follow up servicing and support.

Resources to research? Way too many to even start. What, specifically, are you considering? If you could narrow the scope, you would probably tease a response or two from the regulars.

Good luck with your conversion.

[mattsiegman]

this seems like a silly topic. .NET can be open source. .NET is a way to code and a coding framework, open source is a philosophy that code should be viewable by all.

It really depends on what kind of server they're using. On a windows server, I'd go with .NET [I prefer C++, but ASP would probably be best in this case]. On a Linux/UNIX/etc. server, I'd go with a PHP or Perl solution.

I personally prefer Perl for my web apps.

[Dab]

this seems like a silly topic. .NET can be open source. .NET is a way to code and a coding framework, open source is a philosophy that code should be viewable by all.

I admit my ignorance on the subject (that's why I have made the post), and apologise for my looseness of terms. My little knowledge of .NET is that it allows integration of MS's various technologies. I guess my point is more the arguments for using a proprietary system at quite some cost over-all using only MS proprietary services (including web hosting), versus open source with its many free technologies and overall lower costs to impliment and possibility for Unix based hosting and scripting. I do know that there are pros and cons for both. I am naturally somewhat inclined to unix based systems, as that's all I really know.

It really depends on what kind of server they're using. On a windows server, I'd go with .NET [I prefer C++, but ASP would probably be best in this case]. On a Linux/UNIX/etc. server, I'd go with a PHP or Perl solution.

I personally prefer Perl for my web apps.

I guess, this is the crux of it. They have to make up their mind what kind of server they want to run with. I would like to persuade my customer (the creator of the software) to persuade their customer to run with Unix especially seeing that the software has to be rewritten for the web. I was hoping to get a list of pros and cons, and hopefully persuade him to run with Jaguar (as my client himself does with his own site!). At the same time, I would like to be fair.

I would really like a pointer in the right direction to be able to assess the two options myself as I don't know enough about .NET.

[Dab]

Oh, and thanks Spathiphyllum for your reply. I guess I've provided, I hope, a clearer indication of what I'm wanting in my reply to Matt. Any assistance is appreciated.

[Spathiphyllum]

Dab,

Since you are "going web" with the apps, I'd suggest you direct the first inquiry to Netcraft and look at the stats and trends of webservers. While NCSA began it all and is the foundation of web serving, Apache has a dominant share that isn't going away. Considering also the security implications of such a resource and the questionable history of Microsoft, you can see why Apache appeals to so many. Like a hand in a glove, much R&D public and private has been co-developing with Apache as it proves to be a terrific serving paradigm. Microsoft and its more proprietary innovation just haven't kept pace. .NET, as I interpret things, is a way for Microsoft to try and coopt yet another data exchange mechanism (hey, they "invented" it) into its more complementary web serving software though .NET is not exclusively for MS as pointed out by Matt.

A few years ago I was in a similar state as you from a developer POV, yet still quite inexperienced with no finished products. I started with Frontpage and VBasic and felt too limited by Microsoft's non-standardized ways of doing things. After about 6 months of learning, I decided that I wanted another option. I spent the next 6-12 months or so researching various webserving paradigms with various backend support... the conclusion? *nix/Solaris with Perl (still considering PHP but life is too short to use it all) on Apache continues to provide more tools and options than I'll ever be able to experience, much less master. Personally, I don't want MS determining "where I will go today" and the non-MS technologies seem to suit me best though I'm throwing terms around here a bit loosely.

I've never used .NET and don't see using it any time soon. It may be great but I'm a mere mortal without the time or resources to experience it all or convert what I have. That's one of the biggest obstacles and the one behind which you find yourself... where do you commit your limited resources with the unknown of IT and developing protocols and dynamic challenges.

This may be more philosophical than anything so I apologize for my meandering. The Netcraft survey, however, is not nebulous so your final solution may best be determined by the server you want (on the hardware you trust) that may be instituted affordably with ready support. It will be difficult to provide a simple solution to your question so expect this thread to continue for some time as others debate both the tangible and esoteric. Without knowing every nuance of everything that evolves, I try to follow strict, generally accepted guides that aim for the middle of the road and, too often, MS veers. I cannot afford such unpredictable diversions from a company that doesn't have to care about me and sometimes operates on a whim without providing adequate support when I must plunge ahead with a different timetable from theirs. But I digress.

[Dab]

Thanks, Spathiphyllum, you've been very helpful. I knew that there were pros and cons, but just wanted a bit of a steer. Thanks for the help.

[Spathiphyllum]

Dab,

I'm glad you found the philosophizing (and link) productive. I hope you'll post the outcome to your final path when that day arrives. I'd be curious to know if your audience was receptive to your pitch, whatever the final choice.