Again I bag to differ. My hypothesis is that Apple just followed the most vocal people of the Wonder community. This was a very comfortable decision for then because it freed them of investing in tool support. If the same people would spend the same mental and vocal energy on supporting the old WO tools, we could be in completely different environment now. You're overlooking the other possibility, which is that Apple maybe isn't WILLING to invest in WO tools, and the longer they choose not to, the higher the risk that a WO tool would break in a future release, which would potentially put the entire framework release at risk. In this interpretation of events, WOLips freed the core frameworks to grow with substantially less risk. As far as supporting the old WO tools, I'm not exactly sure how we could have supported them. Could we have begged Apple louder to replace them? It had been years since anything really had come out of Apple in this regard. None of the Apple tools support a public plugin architecture, so begging was really the only other choice. So it was either that we try to provide nice replacements to the tools (which is the route we chose) or we beg louder, which hasn't had much impact on Apple over the past 5-7 years.
Again I bag to differ. My hypothesis is that Apple just followed the most vocal people of the Wonder community. This was a very comfortable decision for then because it freed them of investing in tool support. If the same people would spend the same mental and vocal energy on supporting the old WO tools, we could be in completely different environment now.