News for hackers. Stuff that matters.
Re:Why Textmate 2.0 is not Developed in the Open by gecko on Wednesday January 06, 2010 @09:49AM (#1034781)
Ah yes, TextMate: the text editor that proves that the patent-pending Duke Nukem Development Model™ need not be reserved for video games.
Re:Why Textmate 2.0 is not Developed in the Open by teilo on Wednesday January 06, 2010 @11:36AM (#1034996)
There is a significant difference between a 3D game and a utility, namely, how closely the development cycle must track the platform upon which it is to be released.

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.

Re:Why Textmate 2.0 is not Developed in the Open by silencio on Wednesday January 06, 2010 @03:45PM (#1035706)
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.
Re:Why Textmate 2.0 is not Developed in the Open by Zev on Wednesday January 06, 2010 @11:05PM (#1036464)
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.
Re:Why Textmate 2.0 is not Developed in the Open by silencio on Thursday January 07, 2010 @06:51AM (#1036886)
> 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.

Re:Why Textmate 2.0 is not Developed in the Open by Zev on Thursday January 07, 2010 @04:14PM (#1038046)
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.

Re:Why Textmate 2.0 is not Developed in the Open by silencio on Thursday January 07, 2010 @05:34PM (#1038191)
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.
Re:Why Textmate 2.0 is not Developed in the Open by Zev on Thursday January 07, 2010 @05:54PM (#1038237)
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}.

Re:Why Textmate 2.0 is not Developed in the Open by icey on Wednesday January 06, 2010 @11:30AM (#1034977)
I am trying to think of a time that a project has gone dark like this to develop the "next awesome version" and succeeded.

I can't think of a time where it's worked, but I'm sure there's at least one example of it happening, right?

Re:Why Textmate 2.0 is not Developed in the Open by teilo on Wednesday January 06, 2010 @11:48AM (#1035029)
Emacs. Yeah, it was developed open source, but how many people, honestly, paid any attention at all to the trunk builds before the next major release?

http://www.emacswiki.org/emacs/EmacsReleaseDates

Re:Why Textmate 2.0 is not Developed in the Open by jrockway on Wednesday January 06, 2010 @02:28PM (#1035512)
how many people, honestly, paid any attention at all to the trunk builds before the next major release

How many people used the "stable" version while Emacs 23 was being prepared for release? I don't know of anyone; Emacs 23 had too many useful features for anyone to wait.

Notice how Emacs users had the option of using an "unstable" version before it was released, whereas Textmate users don't have that option.

Re:Why Textmate 2.0 is not Developed in the Open by icey on Wednesday January 06, 2010 @11:58AM (#1035052)
Taking a long time between versions isn't the same as going completely dark between versions though, is it?

I mean, people could see what was going on in emacs as it was being developed if they were curious. And as far as I'm aware, there weren't significant rewrites between versions.

Re:Why Textmate 2.0 is not Developed in the Open by boucher on Wednesday January 06, 2010 @09:09PM (#1036311)
Delicious Library. Took Shipley over four years to ship version 2, and it was rewritten at least once, and possibly twice, before it ever saw the light of day.