On 3/22/06, Mike Marion <[EMAIL PROTECTED]> wrote: > Oh I agree.. I've written some dogs myself. My note about CF though, > was based on my experiences with the server.. it's a massive resource > pig. Just sitting idle... and they wrote it to do some things in > incredibly stupid ways.. how it handles (or did, maybe it's changed in > the last 2 years) email from forms was just moronic.
I guess that's all relative to the specific task at hand. CF does alot of things when idle, and isn't really ever "idle". It was actually entirely re-written from the ground up between version 5 and 6 (when the "MX" moniker was added) from a C codebase into essentially being a J2EE app that can run on any (supported) J2EE container. So along with that you have memory and JVM tuning, garbage collection, etc to worry about. It's unlikely that your average "marketing guy who just wants a fluffy website" is gonna know the first thing about JVM tuning, or even how to architect an application to best take advantage of the underlying J2EE infrastructure (J2EE session clustering for example). Then again, fluffy marketing sites usually aren't doing any heavy lifting anyways. It comes with a fairly decent default configuration and that works for most sites/servers. > By that, I mean, I've seen a very simple form using it that > could've been done in about 15 minutes in perl code and used a > fraction of the resources to do the whole thing. In my world this is a great use for something like perl. A quick task or system admin task that you may want to optimize by hand and just bang out. Larger perl apps certainly have their place too, however, that longer development time may get magnified, depending on the project and how many libraries you can leverage vs hand coding stuff. I'm sure if you live inside perl all day you are much more efficient than me at that anyways > Of course, if you're a power user that uses all of it's features and > don't just do simple pages.. that's another story. I have seen some > pretty interesting webpages developed using CF.. that would've been > pretty hard otherwise. Still requires way more server horsepower to > do the same things though. IMHO - this is where the new CFMX line really shines. You get the rapid application development environment that the CFML (ColdFusion Markup Language) provides, yet you still have access to reach down into anything and everything Java and J2EE and access it directly in your CF code if you want to leverage some of that for heavy lifting or if the functionality has already has been built in Java. Of course, I am a little biased, and this isn't a CF list, but I thought you might find that info useful. If KPLUG ever wanted a meeting presentation on CF, I'd be glad to do one. I've used it in a Linux environment before and even have a case study of a CF/Linux site I worked on (pga.com) and the architectural and scale decisions we made to get the site running and supporting 10M+ pageviews an hour during golf touraments. Aside from that - back to your regularly scheduled programming. -Cameron -- Cameron Childress Sumo Consulting Inc http://www.sumoc.com --- cell: 678.637.5072 aim: cameroncf email: [EMAIL PROTECTED] -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
