This means that for some, imagination is now the limit. We already see lots of blogs, talks, forum posts, and even github discussions being machine-written, where people succumbed to delegate imagination and voice. There even are in the elixir community a few people letting Claude borrow their name and profile picture while handling all interactions. I won’t name them here but I find this very unsettling. I don’t blame them directly, these are strange times and it asks everyone to adapt. This process of adapting can take a lot of weird intermediary shapes. — Ending my elixir exploratory writing

Back in 2006… Mathematica 5.2 and Aquamacs running on OX X Tiger; R and Emacs on Debian while I was writing my PhD dissertation.

macOS applications that has stood the test of time. #apple

Are you after some MP diagrams to stay awake all the night? #tex

/me is listening to “Block Rockin’ Beats” by The Chemical Brothers

Good. Now I know I can lint CONTEXT or plain $\TeX$ file with badness too.

Just switched from Texlab to Badness, by the author of the Panache LSP for Markdown & Co., since I barely use $\LaTeX$ these days (and I don’t need the build/synctex toolchain anyway). Great work as with Panche! #tex

The keyword here is fast. — Fast Filewise Git Blame

Shout out to the author of this blog for his entertaining posts and for such a beautiful designed website: https://www.tobymackenzie.com.

“Modern” is quite a buzzword, but it is justified when talking about Neovim. The project started as a big refactoring of the Vim codebase, throwing away a lot of code and removing support for legacy systems. It uses a brand new VimL parser which is much faster than Vim’s one, leverages libuv for asynchronous IO and is generally much more modular. — Why Neovim over Vim