Well, at least let's be a little more open/honest here.
There were many bugs/issues (some even self inflicted by the team itself) that the team simply
refused to fix even when it was clearly pointed out and a drop in solution was offered.
More recently things are getting better, but for a few years, things were pretty bad
and got very heated at times.
The best example of a total screw up was when the team consciously and intentionally decided
to break 100% of the existing 3rd party libraries between the final 1.0 release candidate
and the final official 1.0 release.
In normal s/w development practices, you just don't do something like that.
(have years of working code, and then break it all between a release candidate and the final release)
This broke years of compability and stability. The team knew this was going to be an issue
and against many pleas from 3rd party developers proceeded anyway
even though there were some very simple alternatives that offer backward comptibilty to
to the vast majority of existing 3rd party.
Think about that again for a moment. This was not a bug, it was not an "oops" or
an untended consequence. The team knowingly and consciously decided
that it was a good idea to break 100% of all the 3rd party libraries in existence.
They thought that breaking all the libraries was a way to force the 3rd party developers
to all update their code for the new way of doing things.
Even after a couple of years since the 1.0 release, we are still fighting issues with this decision
and yet they still refuse to include some backward compability header files to allow
most of the pre 1.x libraries to work on 1.x
--- bill