whether you believe it all or notis another matter, i reckon so long as it can be read by SE then you will be fine
NuvoForum LeaderVPS - Virtual Prince of the Server
Advantages:
1: More likely to work for everyone who visits your site (not everyone uses the same browser).
2: Cleaner.
3: Uses less bandwidth (this is why they reccomend you use CSS, which also cuts bandwidth use).
4: Less likely to break (tags like <font> are depreciated and could be removed completely once the W3C is confident that they aren't used anymore, but sites still using them would break down if those tags were removed).
5: Easier to understand and change at a later date (rather than changing a whole load of font tags, you could just change a bit of CSS relating to a <span> tag and it'd be done a lot quicker).
Disadvantages:
1: Compliant code can, if used poorly, fail in older browsers which don't support the HTML version you're using (XHTML 1.1 Strict got bad press because MS, in all their wisdom, forgot to make Explorer compatible with it).
2: Internet Explorer and browsers based uponb the Explorer rendering engine don't follow any of the current HTML or CSS standards correctly, thus meaning that you have to use cheap tricks to get the right effect.
While this doesn't usually make your code any less compliant or make it screw up in other browsers, it does mean more work.
3: Many commercial web design applications don't support standards compliant code.
Dreamweaver and Frontpage are two very good examples of this (Frontpage creates IE specific code and Dreamweaver doesn't do a great job of it either).
PHP, CSS, XHTML, Delphi, Ruby on Rails & more. Current project: CMS Object. Most recent change: Theme support is up and running... So long as I use my theme resource loaders instead of that in the Rails plug-in. Release date: NEVER!!!
If you plan for the site to last for a few years and don't want to have to re-code the whole darned thing, use compliant code.
That's my advice. Take it or leave it, but don't ask for nothing else.
For the last few designs ive done theyve all been XHTML Strict - all compliant code. I will probably do it for all my future sites I was just curious as to what the main advantages are
Hah, that's better than me.
I just use CSS and a mix of HTML/XHTML.
And then, I don't even know if it is strict or transitional. I guess I'm a pretty bad coder.
Not that I code very much lately, except for the VBA i have been doing for my ICT coursework in Excel, for which I just completed a 1000 line Macro.
Python
Forum LeaderThe Royal RAM
Comments
whether you believe it all or notis another matter, i reckon so long as it can be read by SE then you will be fine
1: More likely to work for everyone who visits your site (not everyone uses the same browser).
2: Cleaner.
3: Uses less bandwidth (this is why they reccomend you use CSS, which also cuts bandwidth use).
4: Less likely to break (tags like <font> are depreciated and could be removed completely once the W3C is confident that they aren't used anymore, but sites still using them would break down if those tags were removed).
5: Easier to understand and change at a later date (rather than changing a whole load of font tags, you could just change a bit of CSS relating to a <span> tag and it'd be done a lot quicker).
Disadvantages:
1: Compliant code can, if used poorly, fail in older browsers which don't support the HTML version you're using (XHTML 1.1 Strict got bad press because MS, in all their wisdom, forgot to make Explorer compatible with it).
2: Internet Explorer and browsers based uponb the Explorer rendering engine don't follow any of the current HTML or CSS standards correctly, thus meaning that you have to use cheap tricks to get the right effect.
While this doesn't usually make your code any less compliant or make it screw up in other browsers, it does mean more work.
3: Many commercial web design applications don't support standards compliant code.
Dreamweaver and Frontpage are two very good examples of this (Frontpage creates IE specific code and Dreamweaver doesn't do a great job of it either).
Current project: CMS Object.
Most recent change: Theme support is up and running... So long as I use my theme resource loaders instead of that in the Rails plug-in.
Release date: NEVER!!!
The Royal Ram
That's my advice. Take it or leave it, but don't ask for nothing else.
The Royal Ram
I just use CSS and a mix of HTML/XHTML.
And then, I don't even know if it is strict or transitional. I guess I'm a pretty bad coder.
Not that I code very much lately, except for the VBA i have been doing for my ICT coursework in Excel, for which I just completed a 1000 line Macro.