Because designers all to often use programs that generate 100 gifs to present one page (high bandwidth), and NEVER use include files (whether it's ASP or PHP) to simplify headers, footers, nav bars, client-side script, etc. These code generators also fill up the page with font and tags when CSS is better and easier to maintain. Also, the directory structure is usually unusable so when a programmer has to go in to add some functionality to the page, all the links have to be changed.
If you're a designer: PLEASE PLEASE PLEASE build the pages so we can REUSE them, instead of making copies of copies, so that you have to change 300 pages to edit the privacy policy link at the bottom of the page....
MAYBE YOU SHOULD LET A PROGRAMMER CREATE THE BASICS OF THE PAGE, and then have a designer come in and pretty it up. Code maintenance is a much bigger cost than creating it in the first place, and a good, hand coded page utilizing CSS, attached script files, and includes is SO much easier. The processing hit (of using server side code) is negligible (well, OK, maybe with IIS it takes 4 times as long to process a page just by calling it.ASP instead of.HTM, but you can ASP2HTM lots of pages to save on that) especially with the processing power of today's servers.
I totally disagree with the Coward and his attitude (that's nice, calling someone a moron because you don't agree with him). Many clients say "I want these features and I don't give a #@$% about Netscape 4.08 since it's gonna cost me more to have you develop it. I'm happy to satisfy 9?% of my possible audience."
Others say "I want it to do everything (DHTML, CSS, ActiveX, Flash, integrated Authorization and Authentication, SSL etc.) with every browser" until we tell them the price of the development, and the potential bugginess....
It's easy enough to say "make it standards compliant", but the different browsers implement standards differently Take CSS, for example, and how about printing? Why do you think there are so many pages devoted to cross browser functionality? BECAUSE IT'S HARD AND TAKES TIME. TIME MEANS IT COSTS THE CLIENT.
Not every client has the $ resources of an Amazon or an Ebay. Do you work for real live clients?
Slashdot Mirror
If you're a designer: PLEASE PLEASE PLEASE build the pages so we can REUSE them, instead of making copies of copies, so that you have to change 300 pages to edit the privacy policy link at the bottom of the page....
MAYBE YOU SHOULD LET A PROGRAMMER CREATE THE BASICS OF THE PAGE, and then have a designer come in and pretty it up. Code maintenance is a much bigger cost than creating it in the first place, and a good, hand coded page utilizing CSS, attached script files, and includes is SO much easier. The processing hit (of using server side code) is negligible (well, OK, maybe with IIS it takes 4 times as long to process a page just by calling it
I totally disagree with the Coward and his attitude (that's nice, calling someone a moron because you don't agree with him). Many clients say "I want these features and I don't give a #@$% about Netscape 4.08 since it's gonna cost me more to have you develop it. I'm happy to satisfy 9?% of my possible audience."
Others say "I want it to do everything (DHTML, CSS, ActiveX, Flash, integrated Authorization and Authentication, SSL etc.) with every browser" until we tell them the price of the development, and the potential bugginess....
It's easy enough to say "make it standards compliant", but the different browsers implement standards differently Take CSS, for example, and how about printing? Why do you think there are so many pages devoted to cross browser functionality? BECAUSE IT'S HARD AND TAKES TIME. TIME MEANS IT COSTS THE CLIENT.
Not every client has the $ resources of an Amazon or an Ebay. Do you work for real live clients?
Hex time is already available: Hex Headquarters