BBEdit still has the best multi-file search-and-replace feature of any editor I've ever used. Tons of options, a visual pattern builder, multiple simultaneous search source directories and the option to save search sets, it's saved me innumerable hours of tedium.
I still keep updating it (been using it since 1.x days) for multi-file search as well, even as the rest of my workflow is tmux, nvim and other command-line tools. BBedit's diff tool is excellent too.
I've previously been able to edit large files with vim, emacs as far back as 1998 and other editors on OSX for a while, what would happen in editors such as hexfiend, glogg, pilotedit,vim,emacs etc ?
Unless bbedit available for another platform that wasn't osx ? (my history is shady).
The multi file search and replace is so good that it kept me coding Python in BBEdit long after I should have switched to something better suited to the task.
* tapping on a folder icon and then a bunch of rumbling in the cage from hard drives back then.
* the excitement with controlling a virtual world using a graphical user interface.
* Doing the floppy shuffle on a system without a hard drive.
We were still at the stage of "all computers are miraculous" and along came the mac with graphics/UI consistency and quality which just seemed impossible.
I still find computing amazing, but those early days of wonder and awe were great.
BBEdit is such a wonderful app. I'll be honest, I have never used it as my primary editor -- I grew up on TextMate and the like -- but if I want something reliable and performant, nothing is better.
I pay for a license every version just because I want to support teams building apps that have been around for as long as BBEdit has been around and that are so thoughtfully designed and lovingly supported.
When you talk to BBEdit diehards, they talk about it the same way people speak of their very favorite and most-treasured tools, and even in the realm of text editors (where, let's face it, we're just downright passionate about our editor), that is rare and wonderful to see.
Yeah, it’s large file performance is unparalleled. As well as the way it does search and replace. As I said, it’s not my primary editor, but if I need to handle a large file, it’s where I start and end.
BBEdit is the first programmer's editor I used. It was 1998 and I got a job at a Portland design agency who ran Linux on servers and macOS 9 on desktop. BBEdit's powerful search and replace function was also my first encounter with regular expressions. Later I switched my desktop to Linux and my editor to Emacs, but I kept returning to BBEdit for its search and replace, while I was still ramping up on Linux.
BBEdit stokes super fond memories for me and I wish the best of luck to the project into the future.
Same here (college, late 90's), but forgot it was still around until recently (sorry). A couple of years ago I was getting annoyed with the common editor used by my co-workers and searched and found BBEdit was still maintained. Got it back and still has the nice search features.
BBEdit is one of those classic software products that will always be associated in my mind with the Macintosh. Been a Mac user for 31 years. A shame that other Mac shops from that era like Ambrosia or Casady & Greene didn't make it.
Ambrosia SW! I spent a lot of my high school days playing their games, hadn't thought about them for years. (Also was a big fan on Freeverse SW's games and will always have some of the insults from them in my head.)
when did ambrosia leave the scene? i remember emailing them maybe 5-10 years ago asking about all the EV keys i bought. I really enjoyed most of their games, but ev:nova was [at least] 3 games in one.
I remember BBedit, RESedit, and the one i miss the most, graphic converter. It had a folder sorting slideshow mode, and it was, non-hyperbole, the best feature of any image app ever. slideshow shows a picture. You could press Command+number, and the image would be moved from whatever folder the slideshow was in to whatever folder you set up for that number. So if you were a photographer, you would load your images from the camera, and have "keep", "maybe with edits", and "archive" folders set to 1, 2, and 3. It was so fast and so slick. IrFanView is an amazing piece of software, now a little long in the tooth as well, that does many amazing things with directories of images - but it still can't do sorting slideshows.
P.S. Endless sky is pretty cool. there's a few EV clones out there, a couple on steam. Of course Space Pirates and Zombies tried (and the second one even made a huge leap like ev:nova did!), but none of them have the software engineering charm that made EV what it was. Fully extensible, user editable, great sounds (although some of the new ones just wholesale rip off the EV sounds), 6 different ways to play through and get an actual ending, etc.
I always forget the names of the EV clones whenever someone hits the nostalgia button, so i'll just say "before halo, bungie made marathon which was so far ahead of its time that even unreal couldn't touch it until unreal: Tournament.
Hard to point to an exact date; it was a gradual process. The web site finally went offline in mid-2019, but the company had been essentially dead for years before that -- they hadn't released any new software since 2013, or any updates since 2016. Most of their game library never even got ported to OS X, so one could argue that the process started as early as 2002...
> I remember BBedit, RESedit, and the one i miss the most, graphic converter.
I remember naming a function that sanitized sketchy (in the charset sense) email content “zap_gremlins” — this was about a decade ago, and probably about a decade after the last time I used BBEdit. I’m a Sublime guy now but fond memories.
And in the newest edition the converse option "Precompose Unicode", when Word once again decides that there shouldn't be any national characters and produces composed sequences that won't render in the browser with custom fonts. (It's pretty much as essential as "Zap Gremlins" had been – and about as god-sent, especially for work in multi-lingual context.)
Word likes precomposed Unicode characters. Decomposed characters will make the spell check go wild. macOS, on the other hand, loves decomposed characters, and will insert them in places where you don’t want them.
BBEdit is my Mac version of the "Notepad.ext". Been a user for over a decade by now and still love it, albeit after macOS Monterey upgrade it has become significantly slower in app loading time (from a fraction of second to 1-2 seconds sometimes, irregardless of the size of the files that were previous opened of the number of files previously opened, less than 10 usually for me)
I think i even paid for it back in the 90s, when it was legitimate shareware. I don't think i "cracked" it with resedit like so many other things on mac OS 7/8/9.
If you stack up all of my software (not game) purchases, and label them "for Apples" and "for Windows" i think macos wins. And that predates OS X desktop, even. Something about the apple ecosystem made me want to spend money to support it. So i take full credit for apple being [one of] the first trillion dollar companies on earth.
So I guess I used BBEdit for 28 years. I started on System 7? I think. And I finally stopped last year when I switched to CotEditor, wanting something more macOS native.
It's still installed, though. I was mildly annoyed that I paid for a version 14 license and then about 6 months later version 15 came out and my license didn't work in it.
It's probably still worth the money, but I'm enjoying CotEditor for my basic text editing needs.
Edit: My version numbers may be confused. Whatever they are, my license only worked for less than a year. I did ask support if I qualified for the next version, and they said no.
> I was mildly annoyed that I paid for a version 14 license and then about 6 months later version 15 came out
The current version of BBEdit is 14.1. Maybe you're getting the version numbers confused here. (BBEdit 14 came out in mid-July of 2021, and while a version 13 license would indeed not work in it because new versions require new licenses, the web site clearly states you can upgrade from BBEdit 13 for free if you bought it on or after January 1, 2021. IIRC, Bare Bones has always been fairly generous in this kind of upgrade policy.)
> And I finally stopped last year when I switched to CotEditor, wanting something more macOS native.
BBEdit has always been a native Mac program, so I'm not sure what it is you're trying to get at here?
If you quit BBEdit it'll restore the state to where it was when you left. It recovers documents after crashes. You can even turn on an option that lets you recover "untitled" documents that you explicitly clicked the "Don't Save" button on. I suppose BBEdit isn't literally saving to the open file as you go, so if that's actually what you want, it's a strike against it. I'd have to put some effort into actually losing data with BBEdit, though, and I think on balance I'd prefer "don't let me lose unsaved changes unintentionally but still let me close a file without saving or revert to the version on disk if I confirm that's what I actually want to do".
By "Versions" I'm not entirely sure what you mean, but BBEdit integrates with the Mac's native file versioning at a level that I don't think I've seen any other editor do. You can select "Search > Find Differences > Compare Against Previous Version" and get a diff just the way you would if you were comparing versions in Git or Subversion.
I love CotEditor too, it has basic Markdown's syntax highlighting which is all I need to take daily notes. It also has a CLI with args to jump to specific line and column which I use in combination with FZF to search and jump to matches in my notes.
I'm amused that we've gotten to the point where BBEdit no longer feels native because it's so old and clunky and everything else has a more slick, modern design.
My needs are very basic, so I didn't give Sublime much of a look. I specifically wanted something macOS native, and CotEditor was one of the few, possibly the only, that supports Versions. It does everything I need it to.
BBEdit has a pretty strong ethos of "giving the user what they need" over what they ask for or what they want. Additionally, they obviously put a lot of thought into the interface and how it works. A lot of editors have flash, and an option and plug-in for everything, but I can't find things, the flash distracts me, etc. It feels more GNOME-ish in giving the users fewer good and well-placed options and less KDEish in haphazardly throwing in the kitchen sink somewhere in the menus and preferences if you can ever find it--but I've created a false dichotomy, because BBEdit kind of throws in the kitchen sink without ever feeling like they're just jamming in icons, menu options, and preferences incoherently--best of both worlds. In BBEdit, in addition to the logical placement and thought, they have a well-maintained PDF manual which I've gone through pretty thoroughly a few times. I like to learn software like this, RTFM, then I know what it can do. I don't like to "easter egg hunt"--pick around menus, or pick around half-baked after-thought "documentation" on the editor's website. I don't invest serious time into programs that don't seriously invest in their documentation. For me, it just makes a huge difference in learning a program and knowing what it can do.
I also just don't want to curate a mini ecosystem of plugins or extensions to accomplish my work--with varying documentation standards, interoperability, design aesthetic and sensibilities, and so forth. I want want 1st party solutions coherently integrated, full documented and integrated, and BBEdit goes this route, by and large. This isn't a magic bullet, but a different set of trade-offs that I strongly prefer, as you can find just the extension that works just right for you in a thriving ecosystem, but for me, I prefer 1st party "maximize the utility under the curve" kind of thinking, the same way Debian or a Linux distribution makes packaging uniform. Yeah, it's not compiling qmail with my custom set of patches, but as a coherent system, it delivers a lot of value.
I use BBEdit as my primary editor for everything, but I tend more toward SREish stuff than heavy development. BBEdit is really in a league of its own in what you might think of as the editor equivalent of "soft skills" like coherent design, ease-of-use, documentation, first-party features not reliant on extensions as opposed to having to use plugins and third party code (with the associated drawbacks, but you really can't match the functionality of your perfectly crafted editor via 20 carefully chosen plugins if you're willing to make an editor your lifestyle) etc. Unfortunately, in practice, that does tend to lose to "hard checkbox features" and extensibility.
This is a really great summation of BBEdit's appeal -- and also a really great summation of why it won't work for many folks. BBEdit is fairly easy to script and customize, but it's not extensible in the "add entirely new UX" fashion that Vim, Emacs, and VS Code are.
I'm not a programmer, but I switched to hand-coding my personal website a few years ago and started using BBEdit more and more. The text filters, multifile search-and-replace, and clearly written manual have been especially helpful. The program is a pleasure to use.
I’ve been using BBEdit more and more these days. Used a lot of TextMate, Sublime Text, VS Code, Emacs… but BBEdit seems to work everywhere and it starts up fast.
I’d also say that it’s one of the editors that suffers from the fewest misfires—in Emacs I’ll accidentally trigger some weird command by screwing up a sequence of shortcuts, or in TextMate I’ll accidentally expand some weird macro by holding the shift key down too long, and in various editors, I’ll fight against autocompletion that is sometimes too aggressive. BBEdit, for whatever reason, just gets out of the way and lets me write text.
I’ve used BBEdit since, I think, 1997. Paid user since 2000, or so. Even since I retired from writing code regularly, every Cloudflare blog post’s first draft I’ve written started in BBEdit. Real or imagined, can’t stand the typing lag in any other editor I’ve tried to use. Great product!
You should write a blog post on BBEdit to help them get more users! Do you think the high quality of cloud flare may some way have been inspired by your use of BBEdit?
I went from BBEdit Lite back in the MacOS 8 days (used SaintEdit in System 7 after I got it off a BMUG CD-ROM) to TextWrangler and eventually in like 2014 finally paid for BBEdit.
no matter how many times i try to switch to vscode, i always come back to bbedit. no other editor i've tried feels as natural for coding – except maybe visual c++ back in the day.
This was my first development tool on a mac, which I was using much against my will at the time, finding comfort in Windows and SGI machines in my youth.
It was a life-saver as an application, the dev tools available on Macs those days were ... unreliable to say the least.
When I joined the Mac world in the late 90s, BBEdit was one of the first things I downloaded and installed. It wasn't until I started coding with it in about 2001, though, that I realized how limited it was vs. some of the other editors I was toying with at the time.
What made me delete it was an episode of data loss in 2005. I hadn't saved; the Mac crashed; I lost data because BBEdit amazingly had no autosave or document recovery features. I wrote in, expressing frustration. BareBones' response was "yeah, we might do that someday. Just save a lot."
I switched to TextMate, and then to Sublime, and eventually to Emacs (though I only rarely code anymore). I never owned a BBEdit license again. In that time -- ca. 2005 -- TextMate was picking up a LOT of BBEdit users for various reasons. Of course, now TM is dead and BBEdit is still here.
I did just check, though. Apparently, BBEdit now brags about its autosave/recovery features. I guess it turned out to be important to them after all.
I've had a BBEdit license since ca. 2000. And I've always been happy to pay for license upgrades as new major versions are published, even though for programming I've primarily used Emacs since 2012.
It's still a wonderful tool for working with and transforming plain text.
It depends on what you want and like. I like BBEdit more than Code despite Code arguably being more capable for, er, code, because -- at least for the way my brain works, apparently -- BBEdit is better at editing. Most of what I do with it is technical writing in Markdown.
Having said that, though, BBEdit 14's LSP integration closes the gap in coding for me sufficiently, at least for PHP and Elixir. And there are sort of quirky features like the Unix Worksheet, "text factories," and BBEdit 14's new notebook feature that I'm using a lot.
Yeah, I've used BBEdit for all 30 years and VSCode since it was pretty young.
BBEdit is my "i want all of my text files in separate windows" editor. I have it set that way on purpose. I do this mainly for my own spatial organization reason and the fact that I don't like the way BBEdit handles multiple files in one window. I've just started using the new Notes window, and it is a nice implementation that I've been using at work to keep track of dev projects, one note for each project. Very nice and no manual saving needed.
VSCode is still open all the time for IDE purposes. I need the refactoring capabilities and I would find it really hard to live without GitLens, to be honest. I also really, really like file tabs across the top for development! I'm not really sure why BBEdit never implemented this.
To the question, VSCode is missing a bunch of the cool "text-edity" features that I love about BBEdit. All of the stuff in the "Text..." menu, that is. I'm sure you can get all these things with various VSCode plugins, but I don't want to have to go find all of these things. I just want them there. So for now, it's both open pretty much all day!
For me, I like that a lot of the text manipulation stuff I use is built-in to BBEdit, compared to VSCode where a lot of that responsibility is pushed off to extensions where the quality or consistency can be variable.
One example is hard wrap (like for git commit messages). It seems crazy to me that that’s a third party thing and not built in to VSCode.
BBEdit was my main html editor from 1994. Back when sites were mostly static files, its multi-file search and replace compatible with regex was how I’d apply site-wide updates, at times pretty extensive ones.
Over the years I have used many editors, I have a weak spot for Atom for code today, but I never stopped running BBEdit.
It comes super handy on a weekly basis and is still the only one that can open huge text files easily.
I have a lot of love for BBEdit. That and textwrangler have been on every mac I’ve owned ++. Usually works like a charm and I get a new license with a new mac. I still use it for large files and when I know I need to experiment with regex on someone else’s output.
++ there was that time I had to remove bbedit just to force myself to get used to vscode.
BBEdit was a very good replacement for MPW and Think C's front ends that pretty much everybody bought and used daily. Then CodeWarrior came along and it wasn't really that impressive anymore; still useful for the odd "gremlin" zap or gigantic, bloated folder grep that choked everything else you threw at it back when virtual memory was an aftermarket feature you had to buy from Connectix, but by and large it just sat there on your drive most of the year. It enjoyed a brief resurgence in popularity when Project Builder was forced upon everyone at Apple and folks grew tired of dealing with an impossibly bloated text editor that couldn't keep up with an average 13 year old's typing speed. A lot of teams with the clout to do so simply refused to touch any of the NeXT junk so they didn't have to bother with getting BBEdit to play nicely with PB--the Finder in particular remained a PowerPlant app built in CodeWarrior up through 10.4 I believe.
If your notion of web development is rooted in cgi-bin directories, server-side includes or maybe PHP 2 then BBEdit is more than adequate for your needs. It stopped being practical for anything "modern" anyone would ever want to do around 2005. You can argue that "modern" web development has gotten well out-of-hand and that you shouldn't really need all those ridiculous plugins to accomplish the basic task of putting a blob of HTML on a screen but that doesn't alter the reality of the transpiler quagmire we've let the Facebook kids drag us into one DockerCon at a time.
BBEdit's primary use case these days is giving John Gruber something to romanticize to hipsters who read books about LaserWriters. Blah blah blah Markdown blah blah blah my kids will die if they see a carton of milk on a billboard blah blah blah James Bond marketshare blah blah blah blah blah. The Simpsons shouldn't have lasted 30 years and neither should any piece of software.
