This signals a usability fail in my mind.
Thus, it would serve your fellow developers if you were to annotate the lacking documentation with (1) example code or (2) pointers to the blog postings that you found.
They can. They just prefer to make every Windows developer jump through hoops, as it's so much more cost-effective.
Be mindful of not slipping into the more emotional tone that some have observed nipping at the edges of the HN community.
(I don't mean to sound as if I'm speaking from a position of moral superiority, nor expertise with regard to the topic at hand. Just an observation and suggestion.)
P.S. For the record, I did not downvote anything. That is coming from elsewhere.
Besides that, I think my assessment of the situation is solid. It is much more cost-effective to make your developers (who will follow you, as they have huge investments on your platform already and wouldn't be willing or able to switch) move the direction you want than move in the direction they want. In their position, being able to do whatever is convenient for them regardless of how inconvenient it is to their users, I'd do exactly the same.
It's a delicate act of balancing your inconvenience of moving along with your vendor and your cost of migrating to another. As long as the second half is kept high enough, they can do a lot of inconvenience on the first.
I mean we've had to buy a shit load of graphics cards to get acceptable performance on our (definitely not shoddy) kit.
Edit: I especially like the assertion that WPF is not fast. Evidently the author has never done much with the 3d transform functionality in WPF -- you can do insanely performant graphically-intensive apps using it. The fact that most developers don't understand how the API works doesn't mean the API doesn't kick ass. I'm not a fan of XAML, but everything else about WPF is really, really nice.