After a long argument with Grammarly this morning, we decided to part ways for a bit. The issue started with Micro.blog’s built-in CSS editor for my blog’s template, essentially a text box containing my CSS.

Grammarly kept insisting on fixing my code. There’s an option to tell it to ignore certain websites, and that was the first thing I tried, but it kept highlighting my CSS in angry red. It also tied up my memory and froze Safari whenever I tried to select all for copy-paste (I edit the code in Emacs, where I have syntax highlighting for CSS). I turned the extension off. Nothing. I got annoyed and uninstalled it… it was still there. I removed it from my system completely, including the additional desktop app they have (for applications like Outlook, which exist outside of the browser), and it was still there, still monitoring every keystroke. It only went away after a full restart.

I like what Grammarly does, and it’s been part of my workflow for a while, but I’m wondering if it’s only because I’m used to it now. Apple introduced its “Apple Intelligence” Writing Tools about two years ago, and I haven’t really been using it. Meanwhile, I do use AI to edit my post, and it catches grammar issues and weird sentences just as well.

I much rather not have AI scan and read my texts except when I give it something I want to be public. The idea that I have a sort of key-logger on my system that reads every single sentence I write is creepy enough (I’m glad it can’t monitor Emacs…). I gave the built-in Writing Tools a run, and I think it’s up for the job, so I’m going to try them a bit longer and see if I miss Grammarly.