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.
And FWIW, my comment about deprecated methods was made with new code for TM2 in mind, not TM1.x code being used on TM2.
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}.
If the game development cycle is too long, the existing hardware will so far surpass your product's use of said hardware that when you release, your product will just look childish.
Not the case with a utility or a programming environment. Witness: I still use vim, even though my laptop has a Core2Duo 2.8Ghz, and dual GPUs. If vim 8.0 took another three years to release, I would not care in the slightest, and would gladly upgrade when it happens.