In summary (things most people seem to agree on):
+ CFMX is easier to get started with (unless you have a VB background).
+ CFMX allows you to do some common stuff with heaps less code and hassle.
+ .NET has more "out of the box" functionality.
Do you really mean this?? I would have thought typically CFMX has more out-of-the-box.
+ CFMX + Java provides the server side functionality that competes with the .NET stuff.
Well architecturally you could use any .NET vs Java J2EE comparison to argue for CFMX.
+ CFMX + FlashMX can compete with .NET's out of the box "web controls" - you could also roll your own if you really felt the need.
And then some. Plus if the web controls are ActiveX driven there is the platform dependency card.
+ .NET's abstraction of code away from the developer can be good or bad depending on who you ask.
Isn't this abstraction trying to emulate what CF has done for years?
+ CFMX provides greater platform independence. Well duh..
None of this is really relevant to me right now. I think I am more interested in things like: + total cost of ownership, + license cost vs. development cost,
The license cost for Pro is nothing in the scheme of things. The license cost of Enterprise or CFMX for J2EE is nothing compared to the J2EE server implementation. Plus you might consider the cost of Win2k/3000 server itself. Which is very expensive.
+ stability and security (I guess both are as good as their environment),
+ long term product future
CFMX success is wedded to the success of the J2EE platform. I think it is a good bet.
I guess what I really need is some "eWeek" style comparison from a non-technical/management perspective. If anyone happens to trip over something like this I'd be very happy to see it.
http://www.cffaq.com/ has some good facts about number of large companies using the technology, and the like. US Centric but good nonetheless. Plenty of great Australian reference accounts to be found.
I know I can & will tell them about all this, but sending them a nice link from an independent source would be perfect for setting the mood.
Difficult to find anyone who really understands both products :(
Maybe I am better off looking for .Net vs. Java comparisons?
I reckon you ought to throw some in there. Cos architecturally that is what your comparing. I'd also note that VB/COM to .NET is not an easy migration -- conceptually they are very different. It is a common misconception amongst companies wedded M$ that there training/upskilling costs will be less going to .NET.
Hope that helps a little,
-- geoff http://www.daemon.com.au/
--- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED]
MX Downunder AsiaPac DevCon - http://mxdu.com/
