I am a GIANT cold fusion proponent, but I can't argue this one.
If you have lots of cash and time, then java is a much better long-term and
scalable solution, if you architect it properly and openly (ie. a mix of
html, jsp/servlets, and ejb's).
Cold Fusion is more for fast-to-market applications that require a lot of
functionality to be built in a short amount of time, or on a limited budget.
But you always pay for abstraction. It doesn't scale as well as java, or
give you the granular control of java.
Is java richer? Yup. Is java more open? Yup. etc, etc. - yup, yup, yup.
But it needs to be pointed out that java's immaturity and cost-to-market of
it's implementations is what has made Allaire a lot of money.
If what you are doing is mission critical, and you can get the funds to do
it in java, great, go to town whole hog. I would.
But if it's not a critical system that is not going to get load-pounded and
need to scale through the roof, then I don't know about you, but I'm the
kinda guy that starts thinking about how I could do it in CF and work on
getting some of that money into my bank account.
:)
John
> --- Brandon Behrens <[EMAIL PROTECTED]>
> wrote:
> Can anyone out there tell me why I should use Cold
> Fusion instead of J2EE?
> Medium size project, oracle db. Money not really an
> issue and neither is
> time.
>
> Brandon Behrens
> Developer
------------------------------------------------------------------------------
To unsubscribe, send a message to [EMAIL PROTECTED] with
'unsubscribe' in the body or visit the list page at www.houseoffusion.com
