No offense but this sounds like a massive maintenance nightmare. Best of breed is good, but when you're dealing with too many technologies it's hard to administer (especially for Web apps) and just as difficult for developers to work as they have to switch between technologies for their work. This means multiple learning curves and constant context switches during the development day (which is one of the biggest losses of productivity in dev). It's bad enough in Web dev in general with the required technologies (Web backend, HTML, JavaScript).

Also as devs leave your team you have to replace with people who have that same range of skills which has got to be difficult as well.

It's good to diversify and understand technologies but IMHO mixing too many of them in single solutions or even a batch of solutions leads to big problems in mainteanance disaster later.

+++ Rick ---



>>Hi Experts,
>>
>>Which will be more practical/beneficial/wise overall for a VFP guy with several years of experience to move on to for a web apps: LAMP or go .NET? Kindly advise me also as to which is being more commonly used.
>>
>>Thanks in advance for any insights, comments.
>>
>>Dennis
>
>Hi Dennis,
>
>you don't have to use either one. LAMP implicates a complete system change from M$ to Linux and .net implies a complete binding to M$.
>So, from my point of view the question should not be: LAMP or .net. You should ask, which language offers me the best possibilities for my future tasks. PHP (as part of LAMP) or C#/VB.net (as part of Visual Studio) or perhaps Ruby on Rails or even JAVA might do the job. Nowadays you do not have to select a complete package and try to use it for everything. We still use a lot of VFP as frontend and Informix as database. System near apps are done in C# and our web-apps are Eclipse-based (JAVA) and also use the Informix DB. However the database is replacable and could also be PostGreSQL, Oracle or SQL Server.
>
>And BTW: there is also WAMP, the windows based LAMP ;-)