But why? I mean... it's software, same as any other application software, its environment may need to be customized for it to run correctly. What if Macromedia took that attitude, saying they weren't going to provide parameter and config files for the JVM... it would die on the vine. It strikes me that choosing your development platform is a lot like choosing your friends... by incorporating either of them into your life you also choose to accept a certain level of responsibility for their strengths and weaknesses. If nothing else, there are social repercussions for befriending certain people... and there are some technological repercussions that come with choosing CF as a platform with which you work.

Hence even Jrun has config files that manipulate its startup process, creating a customized (at least if need be) environment to support it, and the numerous other options they've built in over time in response to our requests. Maybe someone should write the CF equivalent of InstallShield, a framework for installing CF applications, and charge bajillions of dollars for it... in any case, there's a certain degree of responsibility to be taken for acknowledging and shoring up it's weaknesses while benefitting from its strengths.

Or, to put it another way, why not light the candle of installers instead of cursing the darkness of broken types?

Anyway... I don't mean to offend, but to offer a different perspective.

Laterz,
J

On 5/3/05, Roland Collins <[EMAIL PROTECTED]> wrote:

I hope I _never_ write an installer for a CF application.  "XCopy Deployment" is as complicated as I ever hope to have to get with CF.

 

Roland





--
---------------
-------------------------------------
Buy SQLSurveyor!
http://www.web-relevant.com/sqlsurveyor
Never make your developers open Enterprise Manager again. ----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email.

CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com).

An archive of the CFCDev list is available at
www.mail-archive.com/[email protected]

Reply via email to