Comments on: Bloated JavaScript in ASP.NET Validation Controls http://dotnetting.wordpress.com/2007/01/30/bloated-javascript-in-aspnet-validation-controls/ .NET tips, tricks, discussion Mon, 06 Apr 2009 03:58:07 +0000 http://wordpress.com/ hourly 1 By: Mike http://dotnetting.wordpress.com/2007/01/30/bloated-javascript-in-aspnet-validation-controls/#comment-297 Mike Tue, 18 Sep 2007 14:41:33 +0000 http://dotnetting.wordpress.com/2007/01/30/bloated-javascript-in-aspnet-validation-controls/#comment-297 That's the price you pay for using a framework. It's not as if 24K is a burden for most people these days. A one off download to the client means you, as the developer, spend less time reinventing the wheel and more time getting on with stuff that matters, eg. application logic. It's true that 24K of code seems a lot for a very simple form, but complex forms will need the same code too, and it will cached. Because of latency on the web, it's probably faster to download one larger file than multiple small ones anyway. The alternative to using pre-built validation controls is, as you suggest, to wite your own. To make them as robust or as fully featured as a professional while leaving a smaller footprint is a project in of itself. Your clients must REALLY need this 24K of bandwidth to make it worth it. Be lazy. Let your website be 10% slower for the sake of gaining all that you do with a well designed client side framework. BTW, I've never used the Microsoft validators. Because of how badly they sucked in ASP.NET 1, I've always used Peter Blum's. That’s the price you pay for using a framework. It’s not as if 24K is a burden for most people these days. A one off download to the client means you, as the developer, spend less time reinventing the wheel and more time getting on with stuff that matters, eg. application logic.

It’s true that 24K of code seems a lot for a very simple form, but complex forms will need the same code too, and it will cached. Because of latency on the web, it’s probably faster to download one larger file than multiple small ones anyway.

The alternative to using pre-built validation controls is, as you suggest, to wite your own. To make them as robust or as fully featured as a professional while leaving a smaller footprint is a project in of itself. Your clients must REALLY need this 24K of bandwidth to make it worth it.

Be lazy. Let your website be 10% slower for the sake of gaining all that you do with a well designed client side framework.

BTW, I’ve never used the Microsoft validators. Because of how badly they sucked in ASP.NET 1, I’ve always used Peter Blum’s.

]]>