Alaska Alan wrote:
| moral obligation to support it a bit longer than 2 years. Look at the auto
| industry; they gotta keep spare parts on the shelf for 10 years, I
believe.
|
| Tell you what, the best thing we folks can do is to know Fusebox as design
| methodology, and not necessarily as Cold Fusion. Who knows what the future
| holds, say 5 years from now?
Yeah, but what were you doing 5 years ago? I know I was not doing CF, PHP,
Flash, ASP, DHTML, etc..., let alone Fusebox. That's the nature of this
industry. I mean, c'mon, the auto industry has to keep parts around for at
LEAST 10 years, cuz that's how long the products are built to last for.
Software changes all the time, so it's no surprise things are going to
fizzle out when they are not successful, and I think 2 years is generous.
The internet and its culture demand that we update the site monthly, weekly,
daily, etc., and almost always the code behind it changes at least once
every year or two...
Heck, I've had 6 different web-related JOBS in the past two years, let alone
the number of sites I've built and revised :-P
my $1.50
David Huyck
[EMAIL PROTECTED]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
