I believe that the problem that is being that not product or CMS in this case will solve or be able complete all the functionality that "could" be implemented. Anyways, as I see it, if a new CMS can do things that the other can't because of decision made when designing the original structure of the program - than "reinvent" the "wheel".
That's my .02... .pjf
Nando wrote:
----------------------------------------------------------I've been resisting jumping into this discussion, but as i see it, "the wheel" has been reinvented many times, for different purposes and needs. And that's a very good reason to be reinventing it. From my early education, as far as i could tell from watching Fred Flintstone, the first wheel was made of stone. In it's time, that was quite an innovation. But stone wheels, no matter how innovative, are difficult to manufacture, and don't work well on bicycles, for instance.
Whoever came up with the idea of using thin metal spokes in their counter-tension arrangement was an absolute genius. If someone manages the same type of innovation with a CMS, i think they definitely should be reinventing.
:) n.
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com).
An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
