Macromates’ Allan Odgaard has officially announced the alpha release of TextMate 2.0, the hotly anticipated successor to the original alternative text editor. This release marks the culmination of years of waiting for the next release in the lineup.
Since this an alpha release, it definitely is a bit rough around the edges, so don’t get to downloading expecting perfection, but it is very functional and very fast. I’ve been using it since yesterday and it feels pretty much the same, although there are a bunch of changes since the aged TextMate 1.5.10 that you can view here.
TextMate was first released in 2004 and rose to prominence as a viable alternative to BBEdit. Praised for its speed and extensive support for use-case templates called bundles, it has become a major favorite of coders and writers alike. I myself moved to the ‘BBEdit-lite’ TextWrangler a while back because I wanted something faster and lighter but couldn’t wait for the new TextMate.
Some things that didn’t make it into the alpha, but that Odgaard says is coming in the 2.0 release:
- Split views: Yes, I actually had this on the alpha milestone, I’m not overly excited about this feature myself, but I know it’s a very common request, so eventually it should find its way into the application.
- Full screen mode: This is mainly because we are hesitant to go Lion-only so we are holding back with “lionizing” TextMate till we feel confident we can fully drop backwards compatibility.
- Performance: Overall performance is fine, but there are still edge-cases that we haven’t looked into, for example the long lines issue which also exists in 1.x or opening files that exhaust TextMate’s memory space.
- Bundle editor: While a proof-of-concept bundle editor is included, it is provisional, has some flaws, and not how we envision the final bundle editor to be.
- Settings: Not everything in the Preferences window has an effect at the moment and several menu settings are not sticky, some even revert when switching tabs. Those can be set via
.tm_properties— more about this in an upcoming post.