RE: CF VS .Net?

[Jacob Cameron]

I work daily cleaning up other people's code, I do not have the luxury of writing everything that I have to transport to another platform.  If I write it from ground up, then no I do not have a problem either.   Jacob  From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matthew Woodward Sent: Thursday, June 09, 2005 9:38 AM To: list@dfwcfug.org Subject: Re: CF VS .Net? On Jun 9, 2005, at 9:21 AM, Jacob Cameron wrote: However, saying that CF is better because you can run it on multiple platforms does not hold water because PHP runs on more platforms than either one. Pure platforms as in operating systems, perhaps, but that fact that you can't (yet anyway) deploy PHP applications on J2EE and/or .NET gives CF a leg up there. If you're dealing with a J2EE shop being able to hand them a WAR file that they can just deploy on their server goes a long way. Also, I have converted a few sites from Linux to windows and windows to Linux (and UNIX), it has never been smooth. Weird, I've done that numerous times and haven't had any problems, but you have to write your apps in an OS-agnostic way to begin with. The obvious common problems people often run into between *nix and Windows is case sensitivity and drive paths. If you respect case everywhere (file names is the big issue here) and derive all your drive paths dynamically or have them easily editable in a config file for your app, the transition from Windows to *nix or back is uneventful. It's just another web development language meant to confuse us and waste our time arguing and training. Heh--good point. :-) A lot of us forget: The right tool for the right job. Another good point. .NET definitely has its good points and there are certainly cases (as you outlined) in which it could be the superior choice. I just think a lot of people make decisions based on the wrong criteria (it's free, it's Microsoft, what have you) and don't look at the whole of the picture. Matt -- Matthew Woodward [EMAIL PROTECTED]