Well, yes. But as FF+Chrome+Safari have more than a third of the marketshare, you can start writing parts of a website that work better with HTML5. For example, an application that uses the application cache to be usable offline, and tell IE users they could have an offline experience by changing browser. This means that everything still works, but people with HTML5 browsers will have a better experience.
Depends on your target audience. IE has vanishing small market share amongst several groups such as tech savy, non-MS developers, Apple fanboys, etc.
Also, if those capabilities lead to features that vastly surpass your competition it'll be easier to own majority of non-IE customers than it would be going after all customers with generic features.
You don't need every person with a web connection as a customer, you just need enough to be profitable/successful.
But if you cater to poor corporate suckers like me, IE still has vast majority of traffic. It's hard to justify spending any time on features they won't see.
The financial services industry. I work on a large retail trading site - many of our customers and a majority of our clients still visit our site in IE6. They have no choice, and some of them do not even realize they have no choice.
You do have a point. But if you're writing web stuff for the intranet or if you otherwise have enough control over your users to control their browser choice then it's a much better use of your resources to code for the future (FF, Safari, Chrome, Opera) than for the past. Big stupid corporations who still insist on writing all internal stuff to work with IE6 are, sadly, still around. But declining.
