"You wind up with all this controller code spread through hundreds of pages / components"
What does that mean? Controller code? You write a page that does one small section of your entire application, and you use code-behind to abstract the business logic from the presentation. It even makes it nice because you can write an entire application and give the presentation to a graphic designer to work around and he can't mess with the code. Allaire was preaching that 5 years ago. "And most "regular application"s are scary! What's so scary about writing an application? I don't mean to be snide, but it sounds like you haven't figured out how to break up the application into smaller sub-applications. "A lot of VB apps I've seen are very anti-architecture" So what? There's plenty of good ones, and there are plenty of bad ones. But one point I'll concede - I've never seen a poorly written CF application... wait a second, there was that one... "(redneck voice: "Hey y'all, we'll just stick the logic on this here button's OnClick!")" So you don't like event-based architecture? Go look at Mach-II then ask Mr. Corfield what he thinks about it. How about javascript? Why not look at something like the two-selects-related CF tag and tell me that it's not event-based? "IMHO, ASP.NET is a great technical achievement that got blemished when MS's marketing group realized they could sell it as "VB for Web apps," Gee whiz, some of us don't even use VB to write apps. Lordy, I use c-Sharp. 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 7:55 AM To: CF-Talk Subject: Re: Not to start a flame war..... > Using code-behind (asp.net class) and web forms (viewstate) are two of the > MAJOR advantages of using ASP.NET. Code-behind is nice, but I've seen it become a pain in the arse with really big applications. You wind up with all this controller code spread through hundreds of pages / components, and when your model changes, you have to automagically remember which code behinds deal with that portion of the model, and go update them. I think I just have a personal preference for front controllers over page controllers. > It's a web analogy to a regular application And most "regular application"s are scary! A lot of VB apps I've seen are very anti-architecture (redneck voice: "Hey y'all, we'll just stick the logic on this here button's OnClick!"), and code-behind is now letting the same shlock spread to web apps. Struts, Rails, and, well, almost all of the other MVC frameworks make it nigh impossible to do this kind of crap, and ASP.NET all but encourages it. IMHO, ASP.NET is a great technical achievement that got blemished when MS's marketing group realized they could sell it as "VB for Web apps," perpetuating shitty implementations that'll keep hundreds of MCADs employed as maintenance programmers for decades. -- Get Glued! The Model-Glue ColdFusion Framework http://www.model-glue.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:211851 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
