"but on my blog you said something about me not knowing enough (ASP).NET to
have an opinion."

That's not what I said.
"Six months experience in ASP.NET vs years(?) in CF isn't nearly long enough
to present balanced commentary."

I just hate it when somebody trashes something that they don't know much
enough about.  You obviously know more than most people on this list, but
don't you know think that if you had more time of ASP.Net, you might have a
little less obvious bias towards CF?  

Myself, I've been doing CF since 1998 and .NET since 2001.  Having
experienced that I can indeed write code faster in CF, I love it for it's
simplicity of use.  However, I take more time using either VB or C# to write
full-featured objects for massive code reuse.  So I write a new application,
start to write the objects that I need first, and then realize I've already
written them in another place, so I just use them again.  

Not to say that CF doesn't have objects, I guess.

I love the fact that my graphic designer CAN'T touch the code because I'm
using code-behind.  

I love webforms because they allow me to concentrate on one event occuring,
rather than having to write eitehr another page to process a step occurring
or process everything at the same time.

I love the fact that I can write really powerful programs that interact with
the OS when I need to.  I just was helping someone yesterday with an ASP.NET
page that restarts CF when it goes down. 

I haven't trashed CF here, and I don't want to.  But there are serious
advantages that .NET has that CF can't touch. Vice-versa as well.  

The nitpicky stuff is when somebody makes a claim "It's so much harder to
do!"  when they've hardly done it, or even worse, have never done it.

 
Matthew Small
Web Developer
American City Business Journals
704-973-1045
[EMAIL PROTECTED]
 

-----Original Message-----
From: Joe Rinehart [mailto:[EMAIL PROTECTED] 
Sent: Thursday, July 14, 2005 8:10 AM
To: CF-Talk
Subject: Re: Not to start a flame war.....

> Declare the file to write to and write.
> Dim FSO As FileStream = File.OpenWrite("file.txt")
> FSO.Write("Content")

Don't forget to close your stream.  CF does it automatically.  Oh, and
does your operation need a FileStream, BinaryStream, or StreamReader?

This is a nice example of the CF approach vs. the .NET approach.  What
I think makes CF superior here is that you have the "easy" CF way, and
the option to do it the Java way (which is almost identical to .NET)
if you need to.

> "uploading a file... haven't done it, sounds difficult."
> ImageUploadField.PostedFile.SaveAs("Image.jpg");

This _is_ a place I like .NET more - I wish CFFile action="upload" was
a little more powerful.

> "cfdump? they do have debugging, but not a "dump your vars" quickie
> shortcut."
> <%@ trace="true" %>

Last I checked, it's <%@ Page Trace="true" %> - sorry to be picky, but
on my blog you said something about me not knowing enough (ASP).NET to
have an opinion.

The trace is nice, but not nearly as powerful as CFDump because you
can only Write() strings, whereas CFDump can handle complex types.


> "For consuming a web service, you have to create a stub, usually through
> the command-line tool wsdl.exe, or through VS.NET (see: web reference).
> Then call the local stub object just like you would a local class. It's
> not really more code, it's just more work, which is why Ben said it was
> "difficult"."
> 
> Overall I find it as easy to use as anything else in .NET, simply because
> it's treated exactly the same as regular code.

I give .NET points here.  I have found Web Services much easier to
deal with due to the homogenous environment (compared to CF's use of
Axis to produce Java stubs).

> I will say that you're going to be faster writing CF.  I think that
writing
> code in ASP.NET is going to be less bug-prone because of the heavy
reliance
> on the OOP paradigm.  So it's really a matter of time saved now vs.
> long-range maintenance.

I think it's just as easy to write bad .NET code as bad CF code - but
I think in CF, you'll find the bad code faster.
 
> It will take you longer to learn ASP.NET, but that's not necessarily a bad
> thing.  

Why's that not a bad thing?  Paying for people to learn stuff is expensive.

> Experience in any field is worth more than book learning.

Agreed.

-- 
Get Glued!
The Model-Glue ColdFusion Framework
http://www.model-glue.com



~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Discover CFTicket - The leading ColdFusion Help Desk and Trouble 
Ticket application

http://www.houseoffusion.com/banners/view.cfm?bannerid=48

Message: http://www.houseoffusion.com/lists.cfm/link=i:4:211853
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4
Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54

Reply via email to