Originally Posted by penagate
I think when developing today we should be looking at where the web will be in a few years time. What are the trends, who is moving where, so that you target the correct platforms, technologies. Future proofing basically.
Right at this point in time we have a divide between the pure standards route and the IE-compatible route, which is awkward. But if you look at what the browser vendors are doing, they are all moving toward standards-compliance. Microsoft included - IE 7 is a decent move in this direction, even if they still have a way to go to catch up to the others yet.
So if you make an educated assumption that this trend is going to continue indefinitely, the wise choice would be to develop for the standards, because that is what everyone else is doing. This ensures your product is future proof, it minimises the effort required to maintain it in the future (think changing bits of code every time a bug is fixed in IE), and makes it cross platform compatable, giving you a wider market as a result. Developing for IE alone is like shooting at a moving target, because IE itself is moving toward standards compliance.