One of the most worthwhile exercises I recommend here is to consider how you would solve your immediate problem without adding anything new. First, posing this question should detect the situation where the “problem” is that someone really wants to use the technology. If that is the case, you should immediately abort. — Choose Boring Technology

Hooray! racket-langserver got a proper Hover method, which displays full help when pressing K in Neovim, and not only a link to the online doc. #racket #vim

Got nvim-dap to work for all languages I configured (C, Python, Rust), except Haskell for the moment. Together with ’nvim-telescope/telescope-dap.nvim’ and ’theHamsta/nvim-dap-virtual-text’, it provides a neat interface to DAP. #vim

  Current 93, All the Pretty Little Horses.

You can fix spelling error by selecting the first suggested alternative automagically using 1z=. Add this to your (Neo)Vim config, and you will thank me later:

inoremap <C-s> <c-g>u<Esc>[s1z=`]a<c-g>u

(Or bind whatever key you want.) This allows to fix any previous error(s) (thanks to the last bit of magic) using the first suggested entry while you’re in insert mode. #vim

  Lydia Loveless, Let’s Make Out.

What Gemini is doing, is saying “we don’t need no videos, images, stylesheets, nor JavaScripts, because we want to have a lightweight web experience, so we throw all that crap out!”. Fine, sounds great. But why does it require a new protocol for that? Why couldn’t one simply build on top of existing HTTP infrastructure, throw away all the baggage and instead implement a new Content-Type, which existing browsers then could parse? — Gemini is Solutionism at its Worst

Do you feel like Google search results keep getting worse?

Hot end of the week in the kitchen ;-)