[thelist] Re: Why code for standards (martin.p.burns at uk.p wcglobal.com)

Joergen Ramskov mqy4fxax36001 at sneakemail.com
Tue Feb 5 11:54:00 CST 2002


> Time for a bit of devil's advocacy:
>
> Why do we want to code for standards? Is it to avoid the
> extra work involved in multiple sets of coding plus the
> intelligence to serve the correct one?
>
> Now I can see the point of that in a booming economy when
> we're all overloaded with work, but that's not the case anymore.
>
> Times are hard. We're short of work. We have to work our backsides
> off to find it.
>
> So why are we turning away free work handed to us on a plate? And
> more - there are a lot of people who *only* know standards (or one
> browser). Knowing how to code round a lot of them is a competitive
> advantage - sell it to your clients as a 'must have' requirement for a
> professional, and you lock out your competitors.
>
> Who wouldn't do that?

You are only looking at it from the perspective of the independent
Webdeveloper/webdesigner, but if you look at it from a company as a whole (a
company which may have a webspecialists themselves), then standards are
clearly the way to go.

You loose the whole idea (or a lot of it), if you don't use the standards.


--
Joergen Ramskov - Folding for the Cause!
http://arstechnica.com/etc/dcteams/dc_teams.html




More information about the thelist mailing list