Didn't read the news for a week (bc I was returned to office and prefer to sleep more) and reading it now:

— Vim became a LLM slop
— ntfy is a LLM slop now
— systemd is a LLM slop too

What a time to be asleep^Walive  

Looks like my passion to the old and simple solutions made a good thing for me. Time to throw the fuck away the ntfy from my server and use SMTP or XMPP for sending alerts to me.

P.S. Hope, the #Emacs itself willn't become a LLM slop oneday. Replacing it will not be so easy as with ntfy replacement.  

#LLM #slop #SlopWare

@evgandr It seems unlikely to me that #Emacs will ever be #slopified, but I could be wrong. I haven't kept up with the politics around its development, but I have a feeling that at least RMS (and probably most others too involved in its development) are against #slopification.

@Enfors
I used to look at Reddit emacs but now about 70-80% of the posts are about AI/LLMs. So I'm not very confident. They're currently discussing how to deal with slop PRs (slopPieRs?) and it sounds like the main thing stopping them is the licensing aspect.

(edit: what I saw discussed may have just been about org-mode rather than core emacs)

@evgandr

@leadore @evgandr Well, that may well be true, but there's a difference between people who use Emacs, people who make pull requests for it, and its core developers.

@leadore @Enfors Hmm, I see something like that even in the fedi. Since near start of 2026 there are not only 1-2 posts about vibecoding with LLMs inside Emacs, but much more.

Sad state of things…

@Enfors Whoops, I forgot about RMS  Yes, with him, I think, we could be completely calm about Emacs (I mean core Emacs, not packages).
@evgandr Yeah, you can add Lutris to the slopified list :/
@evgandr
Thankfully, people made a non slopified version of ViM.
@Enalys And named it eeEeeeEEEEVim!! 
@evgandr it's really so painful :<
@evgandr why do you think the vim is llm slop?
runtime(sieve): preserve existing line endings in ftplugin · vim/vim@fc00006

Only set fileformat=dos for new files; preserve existing line endings when editing. This satisfies RFC 5228 for new files while avoiding issues with version control and existing workflows. The pre...

GitHub