Quote:
Originally Posted by dosraider
I think that's a bit the problem, aslong you have peeps working for free or from a feeling of involvement, or personal interesse, you can spend all the time you need to bugrun.
Things change when you must pay them, time is money, you only will invest time/money if it's absolutely needed in a site as Abandonia.
Economics instead of love for ol'games.....
|
But you're assuming that they know about standards and they don't want to implement them. Perhaps they know that they exist and no better. They just code their crap and try it in IE or FF or if you're lucky both until it fits. When they have to debug there may be different bugs for each browser, and the workarounds they use for fixing are specific to the quirks and non-standard features supported by each one.
If they followed standards they would have to validate in w3.org only, which gives debugging info instead of when debugging is done by trial and error and the thing just doesn't work. Also standard code is cleaner and more maintainable. The resulting layout should be more or less the same in all standards-compliant browsers. And at the same time browsers would be encouraged to fully support standards and to stop offering particular non-standard features.
The problem is that the human resources people who hire web developers of course know even less about standards, so they don't value it in the curricula, and they won't value more a guy who codes standard than a guy who codes garbage, as they should. (But some day, web standards will turn into a hype just like object-oriented programming, they'll all be fired LOL.)