There are a lot of things that CF can do but isn't really good for. Windows integration through COM is the biggie. There are LOTS AND LOTS of applications that you can take advantage of if you only have good COM interopt, and CF doesn't offer it. Intranet especially, COM is the way to go because you can just make things happen using it.
I still use CF to write websites. It's significantly quicker, its easier and it's fun.
- Matt Small
From: Philip Arnold
To: CF-Community
Sent: Monday, March 08, 2004 2:51 PM
Subject: RE: Dot.net stuff
> From: Shawn Regan
>
> I know more and more houses that are making the shift from CF
> to .NET. A lot of the client we have did not want to use CF
> so I slowly moved towards ASP, PERL, PHP and now everyone
> wants to use .NET.
This always makes me laugh...
If you've got a client that wants a website, then what does it matter
what framework it's built on?
It'd be like saying "I want to buy a car, but it's got to have a Honda
engine in it"
Our clients just want a website, they don't care if it's built in CF,
PHP, JSP, ASP, .NET, cardboard tubes, bits of chewed up paper, or
anything <g>
There is just ONE requirement - it has to WORK!
I've seen so many companies who have said "we NEED our website to be
built in ASP", you ask them why and they just can't answer - usually
because somebody has ready a magazine article or website where it says
that ASP is the best :-P
We work in what we know and what we're comfortable in - which happens to
be CF - if there's something that can't be done directly, then we'll
find a way to do it
I'd rather write 5 lines of code to do something than 20 to do exactly
the same thing <g>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
