Review: 30 days with BBEdit 9 | Cult of Mac

Review: 30 days with BBEdit 9



A while back, I compared BBEdit 9 and Coda 1.5, testing the old warhorse against its young competition. However, while quick overviews are all very well, the only way to find out whether applications are any good is under real-world conditions, so I spent 30 days working with BBEdit, to see if it still doesn’t suck. Find out more after the break…


Although it’s designed for all text-based use, there was literally no way BBEdit was going to usurp the amazing WriteRoom from my writing work—I have to put food on the table, etc. But I did put the application to the test, to see if it could barge all my other web apps out the way and get me through 30 days.

Day 1

Reviewing BBEdit 9 for a British magazine, I start working my way through all of its major features for the nth time, just to make sure that I haven’t missed anything.

I’m starting to hate the text-completion and the preferences UI sucks—when you need a search dialog in your preferences, something has gone terribly wrong. However, the non-modal search/find/replace dialogs are making me grin like a loon, despite the fact that the sensible side of me is well aware that this is the way BBEdit should have been for years.

Day 3

Being a long-time user of BBEdit, I resolutely turned off most of BBEdit 8’s workflow ‘enhancements’, which shoved open documents into a single open window, switchable via a drawer. Today, I’ve decided to try something new: creating a BBEdit Project and using the drawer to switch between open documents.

Overall, the experience is… interesting. Projects are clunky (it’s way too easy to open files) and with the drawer also open, BBEdit grabs an absurd amount of screen real estate, but… I think I like this.

Apparently, though, my eyes are going bad—I today had to up BBEdit’s default text size to 10. I expect to be wearing a pair of binoculars after my next trip to the optician.

Day 4

Yeah, I’m really hating the text-completion now. It’s so massively inferior to equivalent features found in other applications that it’s just not funny. In fact, I hate it so much that it’s being turned off, so bye!

Oddly, I dimly recall talking to the Bare Bones head-honcho about adding this kind of feature when BBEdit 8.something was released. Now I kind of which it hadn’t materialized. The feature tries to be too clever for its own good, but isn’t obviously configurable to mere mortals, and it absolutely sucks for CSS.

Day 7

Still liking Projects, although I wish there was a more space-efficient tab system, like with Coda and Adobe’s apps. The pop-up menu on the toolbar isn’t great, and the drawer takes up too much screen space.

Day 8

Late in the day, BBEdit excitedly tells me it needs to download 15.7 MB of updates, snappily titled BBEdit 9.0.1, to stop my Mac from exploding. (It might have said something about bug fixes, to be honest, but no-one reads those update notes, right?) The install works. My Mac survives. Phew!

Day 10

Projects tip: drop folders and not the contents of folders into the projects pane, because stuff actually updates. This is almost certainly in the manual, and is definitely something I should have realized days ago, but who reads manuals these days? Not me! (The fact that I should is neither here nor there.)

I’m missing the ability to do proper file management in the Projects pane now, though—and so while it’s great for collecting and moving rapidly through a selection of items, you still need Finder for fairly basic tasks.

Day 14

Thought I’d have a play with custom code colors today, something added to BBEdit in version 8. I then swiftly realized it doesn’t enable you to save sets of colors—only revert to the originals if your creation looks like an explosion in a painted fonts factory. That’s a big ol’ fail there, guys. (And, yeah, I know about the third-party add-ons that can sort of automate this, but this feature should be built-in by now.)

Day 17

Loaded up CSSEdit for the first time today, to do a bunch of CSS validation. Sorry, Bare Bones guys, but you should really have added this function to your app. Still, I managed over two weeks before ‘breaking’.

Day 19

OK, so screen real-estate is becoming a real problem with BBEdit Projects—it should have tabs for ‘Files’ and ‘Open’ in the Project pane, or embolden open items, putting the little close icon next to them. And ‘Open Recent Project’ needs its own menu item.

Days 21 through 30

Nothing new happened, apart from a dawning realization that after three weeks, you’re not likely to find new things to say about an app like this. Move along! Nothing more to see!


So, 30 days of non-pain, which is what I like to see, but also 30 days that kind of proved that BBEdit 9 sadly doesn’t entirely have what it takes to convince me to stick with it forever.

I grew to like Projects a whole lot more than I thought I would, but the interface takes up too much space, especially when compared to the streamlined UI of Coda, and the code-completion is just dire. BBEdit 9.something also seriously needs to enable some kind of file management within Projects and let you define syntax color sets.

Overall, the app rates as a ‘good’ on my personal scale, but isn’t quite good enough to qualify for a spangly Cult of Mac ‘recommended’ badge.

For the next part of the experiment, over to Coda. I’ll report back in about a month.


Daily round-ups or a weekly refresher, straight from Cult of Mac to your inbox.

  • The Weekender

    The week's best Apple news, reviews and how-tos from Cult of Mac, every Saturday morning. Our readers say: "Thank you guys for always posting cool stuff" -- Vaughn Nevins. "Very informative" -- Kenly Xavier.

10 responses to “Review: 30 days with BBEdit 9”

  1. John Blackburn says:

    Dear Craig,

    This “My Daily Journal” style may be fun (and convenient) to write, but for reading? Not so spangly.

  2. Rich Dominelli says:

    Glad you are looking at coda next. Could you also do textmate. I recently had to choose and I decided on text mate as a more flexible general text editor vs coda, even though the majority of my work is php/html. I still do a fair amount of scripting and otherwork.

    What sold me was the text expansion (which is somewhat counter intuitive – ie… some manual reading required) and watching several jQuery for design screencasts which really should be part of the textmate marketing material.

    I’m liking textmate, but I liked coda as well and its still a recent enough decision that I am feeling a bit defensive about it. I previewed BBEdit before 9 came out and it didn’t thrill me.

    Thanks for confirming my impressions of bbedit.


  3. Fenton Jones says:

    I would agree about the auto-complete. It has great promise; but there is no good way to control the beast, unless I’m missing something. I do not want something to suggest every word in the dictionary; that is just too annoying for words (pun :-). I do want something that would suggest words from say my glossary items, or other special lists, which I can choose on a document by document basis, as well as specify a default collection of references; something similar to what Spell Catcher does with its references for mnemonics, but better. One can dream. After all, one would hope that a computer could interface better with human concepts after all these years.

  4. Heraclides says:

    I think that text/code completion would benefit from being able to set that the completions are only to come from words in the document, variable/method/etc names, and reserved keywords of the document’s programming language (separately selectable). An additional setting that might help let a user match their needs better, if possible, would be to select what parts of the document you’d like completion to work on (e.g. not in comments). Ideally these should be settable per langauge (you can enable or disable completion in a all-or-nothing fashion per language in the preferences). There are a couple of other tweaks that might help. Personally, I prefer spell-checking on-the-fly for “English” (whatever your natural language of choice is) and restrict completions for computer-language words: reserved keywords and variable names, etc. Others might like the natural language completions, but only in comments, etc.

    Did you try turning completion back on after the 9.0.1. update?: they tweaked the timings for this in the point release.

  5. Craig Grannell says:

    @John: This is something of an experimental format, and this isn’t exactly the most elegant piece I’ve written (not least due to pressing time issues, but I wanted to at least get the thing online, rather than letting it languish on my Mac). However, I think the concept has legs, and so we’ll continue trying it for a while.

    @Rich: No reason why I shouldn’t try TextMate as well. I’ve barely used that application, so this would be a good excuse to do so.

    @Heraclides: Yeah, I didn’t mention that I did recheck completion. Frankly, it’s still rubbish.