That doesn't mean it still doesn't apply. Mac OS X has seen some major API changes and additions in the past couple major releases (that have all happened since Allan announced his working on TM 2.0), and I can see the DNF fiasco repeat itself here. TextMate 1.x won't become completely and unrunnably obsolete, but redoing major features to take advantage of some shiny new API and therefore pushing back any potential release date? It's the same idea on a longer time scale.
API's don't disappear overnight once they've become deprecated. There are API's that have been deprecated since 10.2 or 10.3 but still work on 10.6, for example.
> TextMate 1.x won't become completely and unrunnably obsolete..
Yes, I've already touched on that. ATSUI, used in TextMate, was deprecated in favor of Core Text back in 10.5 but it still works. My point was that the introduction of Core Text caused Allan to go and presumably use that instead in TM 2.0 to get benefits like, oh, him actually working towards CJK text rendering without resorting to hacks, not that the deprecation of whatever APIs he was using before means TM 1.x is no longer runnable on newer versions of OS X.
Not that the DNF vaporware thing was any different, it was a matter of looking obsolete, not a matter of not running at all.
For all we know, Core Text-backed CJK text rendering works fine in TM2 and the wait is for Allan to finish working on other parts of the editor instead.
And FWIW, my comment about deprecated methods was made with new code for TM2 in mind, not TM1.x code being used on TM2.
That was one example of one new major API that Allan's publicly mentioned he will be using in 2.0. Obviously there would be other changes, and obviously you wouldn't just be able to use whatever has been introduced in 10.5/6 to make it happen. Ultimately every rewrite, new feature addition, feature change, etc. has the consequence of pushing back the release date.
I'm not sure what point you're trying to make anymore; I don't believe I've ever (let alone in this thread) said anything that goes against: Ultimately every rewrite, new feature addition, feature change, etc. has the consequence of pushing back the release date.
I only specifically mentioned CJK because A. you mentioned it and B. I remember from other discussions that it happens to be a feature that you want. It could just as easily have been "a shiner way to parse text in order to theme it for display" or #{random-feature-x-that-we-don't-know-of-yet}.
