Live data from Hacker News

TextMate 2.0

github.com

101–110 of 187 posts

Re: TextMate 2.0

#101
I remember liking TextMate back when I used macOS as a daily driver. Glad to see the project is still going. Wish there was a Linux port. :-/

Re: TextMate 2.0

#102
post #11

Earlier quoted context omitted.

Sublime Text, is native, isn't? Sure, much of the API and all the plugin stuff is in Python, but the core is all native C++ AFAIK.

Depends on what you mean by "native". The core is compiled to a native binary. But it doesn't use macOS native text editing or UI idioms beyond the level of windows and menus. If you don't want to use TextMate, you might as well use Visual Studio Code instead, which is closer in spirit to the native Mac idioms and is easier to configure.

I'm not well versed on the specific implementation details of ST, but whatever the ST team does on macOS yields a result that is much closer to a native application than VSCode does through embedded Chromium. The difference in text rendering is particularly noticeable on a non-hidpi display.

Re: TextMate 2.0

#103
Congratulations Textmate team, and thanks for hard work.

I still find textmate the best for my needs:

1. Nice search interface (sorry sublime) 2. Fast and memory efficient 3. Best autocomplete 5. Multi line editing.

But few things could be better: editor tabs not contrast, slow when editing files with very long lines, feature to see memory usage per project

Re: TextMate 2.0

#106
Aww, yay! I've moved almost entirely to VS Code (disclosure, I work at Microsoft but I moved to Code before that and I do not work on that team, though I am lucky enough to work with some of them indirectly), but I still have TextMate for some stuff that it either does better/faster or that I prefer to use out of muscle memory. Beyond that, I will always be a huge fan/evangelist of the app.

2005, the Mac alone had lots of good options (BBEdit to name just one), but I think it is fair to say that TextMate charted the course that every successful text editor has followed over the last 15 years. And I'm not just talking about the ingenious bundle system (the syntax of which VS Code still uses to this day!) or the themes -- stuff like the "mate" command genuinely changed how I interacted with files (it's possible this existed for other editors before TextMate but I'm unaware of it). When TM 2 first went into beta/alpha in 2011, rmate was a revelation. Now, I could use my editor of choice on all my remote machines. VS Code now does this elegantly with the VS Code Remote extension (it works super well in WSL/WSL2), but for those of us who abhor vi/nano/emacs, this is the sort of thing that has really made my life easier. There are more examples I could cite -- but TextMate really paved the way for the editor market we have today.

TextMate was one of the first apps I bought when I became a full-time Mac user in 2007 and nearly 13 years later, it's remained one of the most important applications I've ever owned. I've been using the 2.0 release basically since it was in alpha stage (when it was necessary to have TM1 installed alongside it) and I would honestly probably still use it if the community hadn't all but abandoned it (first for Sublime -- an editor I respect but could never love -- and later for Atom, which was soon usurped by Code).

Even now, for writing stuff in Markdown the way I like to write, my customized TextMate packages remain the best way to do that. I've ported most of what I used to do over to Code but there are some thing that just aren't perfect. (And more accurately, it's hard to get used to something new.)

I bought TextMate when I was still a broke college student, so I took advantage of the student discount offered at the time for TextMate 1.5 or whatever it was. I've always felt bad about that because over the course of the 11 years or so that I used it for my primary writing tool, I easily composed ~5 million words or more into it (one year, 2009 - 2010, I did more than 1 million words -- and this is of prose/Markdown, to say nothing of however many lines of code I might have typed. To put that in perspective, the longest Harry Potter books are ~110,000 words. Suffice to say, I cut back on my writing obligations in 2011 and beyond to save myself from burnout) and an ungodly number lines of bad code across assorted projects (so much bad JavaScript!). I paid a friend initially to customize a plugin he'd made when we worked together for my more specific purposes, and I later maintained/ported those plugins to TM2 (and now, VS Code), but when I look at my TCO for TM versus what it gave me, I can't help but feel guilty.

Congrats, Allan!

Re: TextMate 2.0

#107

Earlier quoted context omitted.

TextMate never had AppleScript integration, AFAIK. Also, I'm not convinced we should ignore those "archaic" technologies, at least in the abstract. Applications can provide "dictionaries" of commands that, when implemented well, provide GUI applications with the kind of "snap together for amazing effect" you get with shell scripts and a host of well-written CLI tools. You arguably can't script the AppleScript-intensi…

AppleScript is a great idea in how everything is scriptable. Unfortunately, the language itself is a horrible abomination from the wild 1990s days of Mac OS... sorry, now macOS... and writing absolutely anything in it is painful. I feel like Apple introduced Automator to overcome the pain of AppleScript, but it never really caught on (I don't even know if Automator is still on macOS.... yep it is, still with the cute…

"AppleScript" can do JS now, but it's so clunky and badly documented that it's barely worth it.

Re: TextMate 2.0

#108

Earlier quoted context omitted.

> It’s possible that native graphical editors will increase in popularity at some point Panic seems prepared to take that bet, with their development of Nova [1], a replacement for Coda. [1] https://www.panic.com/nova/

It better be way, way better than Sublime Text is the plan is to charge Panic prices. Their apps are best of breed but this is a crowded space and they’re competing with free.

I mean, Sublime costs Panic prices. It just doesn't care that much if you abuse its trial.

(Wait, maybe I'm misreading your comment. Are you trying to say "Sublime is free, so Nova will have to be way better to compete with Sublime" or "Sublime wasn't good enough to justify its price, so Nova will have to be way better than that to justify its price"?)

Re: TextMate 2.0

#109
post #12

At the ripe old age of 35, I am apparent a greybeard, because I still use TextMate. I'm just doing light HTML/CSS/JS prototyping, so my needs are easily satisfied, but TextMate is just so light . Launches instantly, doesn't crash, and uses minuscule resources. (Versus the 9 Adobe processes running in the background, even though I don't have an actual application open.) It's just nice to have a completely blank window…

> TextMate is just so light. Launches instantly, doesn't crash, and uses minuscule resources.

I used Sublime for the same reasons, which is to say I understand why people like TextMate over something like VS Code. Being able to do something like open up a 400 CSV without in an editor without the editor choking is just really nice!

Re: TextMate 2.0

#110
post #7
post #3

Great to hear and congratulations to the team. Amazing persistence. I used to be a huge Textmate fan - it was so revolutionary in its time. Unfortunately, I think it is too late. The Google Trends comparison of Textmate, Sublime Text and VS Code tells the story: https://trends.google.com/trends/explore?date=all&geo=US&q=%...

It’s possible that native graphical editors will increase in popularity at some point. There’s probably a niche of people who don’t like the potentially poor performance of Electron-based editors but don’t want to learn (or find that they dislike) terminal-based editors like Vim and Emacs. Who knows? Google Trends isn’t an accurate way to tell the popularity of programming languages either.

> There’s probably a niche of people who don’t like the potentially poor performance of Electron-based editors

Haven't noticed any performance problems with VS Code, since I started using it everyday maybe 3 years ago. I switched from Intellij based editors to VS Code and before that I used vim for a decade.

Post reply on HN