I think it is acceptable to let CF do some things for you. For example, I don't want to go to Java and write the code to handle database calls. Could I? Sure. (Ok, I lie.) But is it a good use of my time? Probably not. I let CF handle that aspect for me and it has never been a problem.
On the flip side, letting CF handle client side JS for me *has* caused me problems in the past. In many cases, I needed to do something different than what CF did. Sometimes this is easy to do, sometimes not. But in the cases where it was easy to do, I've gotten screwed when an CF update changes things that makes my customizations break. Back when CFFORM (and other client side tags, cftable anyone) was added, client side dev wasn't easy. CF was a great help in that area 10 years ago. But guess what? Client side dev has come a LONG way since then. Is it perfect? Of course not. But there are numerous libraries, tools, etc to help make this easier. The simple fact is that CF is *not* a benefit anymore in this area. It is *epic* for handling data integration with client side apps and I'd focus on that instead. On Tue, Mar 4, 2014 at 8:02 AM, Scott Stewart <webmas...@sstwebworks.com>wrote: > > On 3/3/2014 10:39 PM, Gerald Guido wrote: > > Why are people so vehemently opposed so to CFForm? > > > > Many TIA in advance, > > > > Curious-G! > > > > -- > > Gerald Guido > > > > Twitter <https://twitter.com/CozmoTrouble> > > Blarg <http://www.myinternetisbroken.com> > > Facebook <https://www.facebook.com/gerald.guido.9> > > > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:357838 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
