contact us

Use the form on the right to contact us.

You can edit the text in this area, and change where the contact form on the right submits to, by entering edit mode using the modes on the bottom right.


San Francisco, CA, 94160
United States

Writing

On Text Editors — Part 4

Jesse Atkinson

This is the fourth entry in a six-part series on my history of text editors.

The Sublime Text Phase

After a month of interviewing and job hunting, I ended up at TuneIn. This meant moving from Detroit to the Bay area. I started off in VIM, but was eventually convinced by a friend to try Sublime Text again. The beta for 3 had just come out and was pretty stable. So, I checked it out. I was surprised by how much I liked it. After a day of using it, I didn't see any reason not to keep using it. So I did. Once again, I poured myself into the app learning everything I could about it. In fact, I even wrote a starter guide for it that I would give to friends who code or new employees who were unfamiliar with Sublime Text.

Sublime Text (particularly Sublime Text 3 beta) felt like the culmination of years-long frustration at the lack of updates to TextMate and the lack of sensible choices for devs who didn't want to use a fully-fledged IDE. I'd used Sublime Text on and off, but I was never able to use it full-time, day-in-day-out due to how my previous job was.

Sublime Text is, as of this writing, still probably the most versatile and potentially best text editor out there. It's incredibly customizable. It's cross-platform. It's lightning fast. And, it's... ugly.

It's that final point — an intangible one — that most devs seem not to care about. You can customize the hell out of Sublime Text's look and feel with themes. No matter how much I fiddled with it, it felt like putting lipstick on a pig. A very abandoned pig, I might add.

Still, Sublime Text was the best tool for the job. It worked really, really well. It was just not very polished. Then, along came the OS X Yosemite beta.