Ok, time for a coldfusion lesson, and HTTP compression lesson
ColdFusion server is what puts the blank spaces into the code, not the code, not the product. When coldfusion processes the raw code it replaces most of it with blank space, as it interprets it. TuffGuy, the blank lines would equal a carridge return (Carridge Return CR = 1 byte, Line Feed LF = 1 byte), so even if you spent time and removed them all you wouldn't save as much as you might think. You can use some space limiting tags that are built into coldfusion to try and stop it, but they don't work all that well, and for the most part make a royal mess of code. Sorry, but for anyone that has programmed for awhile, turning your code into a mess over a few KB is not very bright. Not only for the people that write the code, but for the customers that buy source code to modify it.
The second lesson is HTTP compression, TuffGuy, unless you are not using a HTTP 1.1 compliant browser you are not getting 330kb of data. You are getting probably 10-20k. We use HTTP Compression here as most sites should!. All html content is gzipped (built into every http 1.1 browser) and then sent to the client, your browser unzips it. TuffGuy, when you see all the spaces in the browser, those are
NOT just wasted blank lines, that is interpreted code. You cannot see source code by just doing view source, you would have to have a source copy of the product to see just what is behind the code. ColdFusion is an interpreted language, in that the source code is "compiled" into pcode and then executed and handed off to the webserver. View source does nothing more than show you the generated code.
So if you have an issue with coldfusion and whitespace, take it up with Macromedia

. I agree that it would be nice if Macromedia would do something about it, but we can't all have what we want.
Hopefully that clears some stuff up!.
Wanna read more:
http://webreference.com/internet/software/servers/http/compression/
http://www.w3.org/Protocols/rfc2616/rfc2616.txt