Quote:
Originally Posted by DirtyWhiteBoy
By reading your posts you clearly sound like a programmer or at least someone who has some advanced knowledge. You come at this from a different point of view, and from where you are sitting, it probably makes more sense AND you are more productive to do it your way. Everyone just needs to do it however they do it best.
|
You're argument isn't totally sound. You're stating people should do things the wrong way if they can't do it the right way. It's not really a means to an end.
You're debate about "the customer doesn't care if it's css or tables" is also a major fluke. Customers don't care if the site is written in PHP, ASP, CF either. That doesn't mean people should just go making all their sites in total static html. 1,000's of static pages with no scripting. Since the customer is only going to see the rendered html page anyway.
There is a right way to write html, for those who have taken the time to learn it. Then there is the "easy out" archaic way of just using tables inside tables inside tables for those who haven't learned the proper way.
Both could theoretically create the same end result, the same layout, the same user experience. However, that is not justification to do things the wrong way.
A lot of people here seem to think the tables vs css debate is an actual debate. Well, it isn't. Tables are designed for tabular data, divs+css are designed for web structure and layout. It's not like we were thrown upon the earth with this shit already around. When html was constructed, these tags were specifically designed for certain things. An <img> tag is designed for an <img>, a <li> tag is a list, etc etc. Go pick up an html book, or take a class on html. It doesn't make a difference the majority of original webmasters used tables for their layout and structure. They did so because it was easier for them. There was no value or attribute differentiation to learn. There was literally no learning curve at all.
You guys want to continue to do things the wrong way, and use certain html tags in a way they were not intended for. That's fine. Just don't expect to be able to put down what you do on a resume or in any list of skill sets. I'd also note that as each year passes, you will exponentially be further and further being the rest of the world in web development. As we move forward, every single year draws a bigger pull for more stricter standards. The longer you keep your head in the sand, the worse it will be if you ever decide to move away from the archaic way of writing html markup.