I haven't jumped on the #Obsidian or #Notion bandwagon. I write in #BBEdit, #OmniOutliner, Apple Notes, #nvUltra and #1Writer. Each has its use. I link all the information with Hookmark. Hookmark's linking is much more general than Obsidian's

J’ai comparé BBEdit et Kate, rapidement et à l’aune de mes usages/besoins :
https://www.patpro.net/blog/index.php/2026/04/05/3845-kate-lediteur-de-texte-foss/

#BBEdit #Kate

Kate : l’éditeur de texte FOSS

Utilisateur de BBEdit depuis 1998, mon univers en matière d’édition de texte est très centré sur macOS. L’excellence de BBEdit, logiciel propriétaire n’existant que sur Mac, est aussi un des facteurs d’adhérence qui freine une possible migration de macOS vers une plateforme plus ouverte (comme FreeB

Cognitive Overhead

So, I made a Q&D benchmark of #BBEdit vs #Kate on macOS, opening and manipulating a huge text file : 915MB, +14M lines, some lines longer than 150K characters.

Kate opens the file faster, but everything else is slower. Kate also has a tunable limit of line length (default to 10K), documents with lines longer than that limit are opened read-only, unless you choose to override the limit when prompted to.
Also, above a given file size, Kate seems to disable some features, probably to preserve performance.

BBEdit has super great text manipulation features, designed with the user in mind (nice GUI to tune a line sorting operation, a complex line extraction, dupe removal, etc.).
Most of these features are non-existant in Kate. But one can achieve very similar results with the great «Filter Through Command…» menu. Just enter your usual grep/awk/tr/sed/sort/whatever command and get the result.

One Writing Tool Per Writing Task | cogmodo

I'm using a different writing app for each task, preferring a single purpose approach for clarity and focus. My workflow includes Drafts for capturing ideas, BBEdit for finalizing and publishing, iA Writer for daily journal entries, Obsidian for knowledge management, and Ulysses for long form writing projects.

@robpike This is one reason I prefer @bbedit on #macOS. It handles massive files with aplomb.

#BBEdit #Mac

Bare Bones Software | Welcome

Ashamed to say, this experiment has not gone very well so far. While #BBEdit seems very nice for working with Svelte, I'm running into issues with React (for my volunteer gig) and Astro (for my personal website).

I'm much happier with it for writing Swift however, and would happily make the switch if I could just find a JSX language module.

My challenge to myself this week is to do all my development work in #BBEdit.

Anyway, tonight I got the various LSPs I use all configured. I've started tinkering with keybindings to be closer to my VSCode/Zed preferences but I guess I can't use "option" as the sole modifier key for any key combos???

#webdev #typescript

@eemeli well. My trusted #BBedit can use and produce them. Of course, so far, it is only because it is more than 30 y old or because I programmed it wrong (not sure which is note common).

But claiming it does not exist is as much utterly modern as claiming that people never had problems with character sets using emails...

Maybe... It depends on your world of all possibilities?

Or like a #BBEdit for iPadOS/iOS.