Meanwhile, he gets so many complaints from dissatisfied users wanting a few core features added to the 1.x version they paid for, that every 6 months he writes plaintive blog posts telling people "I'll release it in another 6 months: software is hard!"
This is the portrait of a project that's being sadly mismanaged into irrelevance, not one that's being carefully honed to perfection.
What I find amazing is the sheer cognitive dissonance of Textmate's popularity in the Ruby community; the same community that has enthusiastically embraced Agile developer practices and whose leaders tend to speak as often about the importance of good project management as they do about good coding.
To that end, I consider features geared toward developers to be critical.
Otherwise, it's hard to disagree that this project is embarrassingly behind schedule. I read once that the first version was only released after numerous ground-up rewrites.
compay means "developer of the application itself" not "developers who use the app."
Really, though, TM1 consistently amazes me in that I don't know too many other five-year-old programs that are still as useful today as they were when they were first released.
The other half of me is pissed off that 1.x has issues that haven't been fixed because 2.x was supposed to fix it, and while I know I don't have a right to bitch and moan and demand this, it's still frustrating. Like how non-fixed-width text does not display correctly (in this text editor). Allan had a blog post back in 2006 about how to fake CJK support and promised 2.0's ground-up rewrite with Core Text was going to solve those issues. 2006. It was also part of a series of posts about how his app was going to go Leopard-only back then, and I'm now just sitting here wondering if I'm seeing a reenaction of Duke Nukem Forever where he's doing re-re-rewrites of 2.0 because of Leopard and now Snow Leopard and...
Since when is holing up for multiple years to work on your commercial project with little outside communication a "considered approach"?
> In my eyes, there could be no TextMate 2, and I wouldn't complain. It is such a sturdy, reliable piece of software [...]
It's both of those things, but that doesn't mean the 1.x branch doesn't have gigantic issues. My personal gripe is that when you focus a project window, the entire project is rescanned from disk for changes. When the files live on a WAN-mounted network share, this makes it unusable.
I stick with TextMate when I can because it's a very good Mac OS X editor, but Vim and Emacs make inroads every day.
"git add -p" is your friend!
Jitkoff works at Google and went on to produce QS "clones" called Google Desktop & Google Quick Search Box: http://googlemac.blogspot.com/2009/06/introducing-google-qui...
I'm still using the original non-opensource QS here with no problems (well at least no probs on Tiger!).
~ bgilmore → uptime
12:35 up 23 days, 56 mins, 5 users, load averages: 0.22 0.19 0.21
~ bgilmore → ps ax | grep Quick
149 ?? S 1:31.43 /Applications/Quicksilver.app/Contents/MacOS/Quicksilver -psn_0_36873
In all seriousness, though, I can imagine the irritation that would be caused by crashes. I've just never experienced them, and I've been on the Quicksilver train since 10.4.1 or so.(I'm a ⌃Space guy myself)
I never even notice the crashes any more, and when it starts acting funny I can Cmd+Q it and it will be freshly restarted in a few seconds.
http://github.com/briancollins/nice_find
It's a plugin, not a bundle (like Ack In Project) so it feels native, it is asynchronous, and it uses git-grep when available. I love it.
http://github.com/protocool/ack-tmbundle
Sure, it's not the native find in project, but it's way faster. Not a day goes by that I don't use it.
In my eyes, there could be no TextMate 2, and I wouldn't complain. It is such a sturdy, reliable piece of software (with comparatively little in the same league), that it seems unlikely to experience a Quicksilver-esque exodus (although that was dead, not just on the slow burn).