Jobe wrote:
Gus wrote:
Write it and make sure it's as you want it in Fx and *then* check in IE.
I know a lot of people in this discussions do defend the fact that good
browsers should support validated code.
We all know that FF is doing this. We all know that IE6 is a nightmare.
This is a logical fallacy.
The axioms are:
* Some competent people advocate validation.
* Many sites are invalid.
* It's difficult to make sites work presentation-wise between IE and FF
* Many sites display well in IE, but not in others.
It's a fallacy to take these observations and extend them to your
conclusion, which appears to be that IE _requires_ invalid code.
Valid code works everywhere, equally well. Invalid code works
variably. _This_ is why validation is good, not because it's a magical
route to good display, but because it's a route to _consistent_
display. From consistency you can achieve good design, but you can't
take a good but invalid design and make it consistent, except by going
in circles.
we should respect the fact that IE has 80 % of the market.
A false argument.
* Who is advocating ignoring IE ? No one.
* Why do you put forward the fallacy that valid code is in some way
damaging to IE?
There's also the well-known observation in software development that it
takes just as much effort to support equally complex features needed by
100% of the market and by 1% of the market. You either do it or you
don't. Once you've done it, any number of users can use it. It doesn't
become either easier or harder just because more or less of your market
care about it.
Bill was able to take the market and to keep it.
It took several years (1997 - 2001) for IE to take the market away from
Netscape. IE is far from invulnerable as the Windows browser of choice.
They're lost and abandoned the other non-Windows markets for IE on Mac
and UNIX already. FF has some tens of % of their core Windows market
already.
Neither FF, Linux,
Opera or Netscape was able to take it away.
I wasn't aware that "Linux" was a web browser.
If we play tennis we have to accept the rules. If we want to play in
the world wide business we have to accept the rules.
Do you have any other meaningless aphorisms you'd like to share?
So it makes much more sence to develop in IE, and check if it works in
FF.
Where did _that_ little non sequitur come from ?
It's wrong, it's obviously wrong, it's empirically wrong and it's not
supported by any of your argument so far.
Developing valid code is easier and quicker (to an acceptable level of
"complete") than developing invalid code. This is a truism for FF in
isolation, for IE in isolation, and most certainly for "the web"
(meaning approximately all likely browsers). In no possible way is
there a tangible benefit for travelling the rocky IE road first.