On 10/24/07, Vince Teachout <[EMAIL PROTECTED]> wrote: > Mainly because he wants to be > sure he doesn't run afoul of any customers that have MS Only shops.
That's a bogus reason. PHP runs on Windows. Or do they only want to run MS languages with MS databases on MS operating systems? > I'd like to do it in Python/PHP. > Are there good solid business reasons for using C# vs PHP, or vice > versa? I think so. I'm not as bright as some of these guys who learn a new language every month and can code in anything, a Jack of All Trades. I'm not as smart. It takes me longer to learn a programming language or platform and takes me a while to see the return on investment of spending all of that time learning. I started messing with Linux in 1998, but didn't offer to support clients with it for a half a decade. I read a couple of PHP books and took a class and played with a couple packages before I felt comfortable enough to offer it to a client. > Or is C# a reasonable way to go? I started reading about DotNet in 1999. I attended the great "Death by PowerPoint" sessions at DevCon Miami 2000. I read a couple of books. I even attended a week of training in Redmond. My impression at the time (2002) was that it was half-baked, version 0.5 and that it would take three versions (real versions, not the stuff MS is renumbering) before it was ready for prime-time. And then five years after that for anyone to have five years of practical experience and write the killer books that would make it easy to master. So, the question for me was whether to go with PHP 4.x, now 5.x, with a half-decade of experience (and real live apps shipped) or to go along with Microsoft on what promised to be their longest beta ever as they reinvented Java 1.0 and 2.0. A big concern was the possibility of the languages becoming obsolete. MS has done this before ;) PHP, on the other hand, is supported by a community, and is more likely to go gently into the night, having a strong community to support previous versions. Now, that's not to say there aren't some top-notch developers creating some great apps in DotNet. Of course there are. But, given the choice of my place in the industry and the apps I wanted to develop in the next decade, the evolution to PHP and LAMP seemed like a better choice to me than the revolution of DotNet. The same argument can be made for Python or Ruby or any of the other non-vendor-specific technologies. Now, bear in mind that what your _client_ needs may not be what you need to offer, and that can be an opportunity, not a fight. [1] Consider offering a subcontract where you hire a DotNet shop, let them design the app with you serving as the general contractor and business-domain expert (think about how to share the risks). Or passing on the client to a consulting company for a finder's fee. There's lots of alternatives. If the client really wants X and you really want to do Y, there's no reason why you both can't get along... [1] http://despair.com/consulting.html -- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
