Why CFFORM sucks

For today's post I thought I would write about the CFFORM tag, and why it sucks. There has been plenty said about why it's so useful already, so I thought something should be said about it's faults.

The main problem I see, is simply that using cfform means coldfusion will inject javascript on to the page. Now that doesn't sound too bad to some of you, but anyone that thinks unobtrusive javascript is a good thing may disagree.

To use an analogy, using cfform is like fast food, it's fast, it's easy, it's cheap, and it gets the job done, but it's sooo unhealthy. All javascript should be in a javascript file so that it's cached and downloaded once, this is the healthy way. And if you use a javascript library hosted at google code, then your users will only download the version of javascript you are using once, no matter how many sites they visit, using the same google hosted code. To put that another way, if you're using jQuery 1.2.3 hosted by Google, and someone else is too, on their site, then any visiter of both sites will only download jQuery 1.2.3 once!