If you use IPython as your REPL of choice when editing Python files in Neovim, and you alson happen to use uv to manage your project, the following keymap might be useful: nnoremap <buffer> <silent> <leader>! :sp term://uv run --offline --with ipython ipython --no-banner<cr><C-w><C-w>. The first time it will install all IPython dependencies, but it will run smoothly on next runs. The advantage is that uv’s IPython is aware of your project dependencies, contrary to IPython installed system-wide (e.g., via Homebrew or uv tool). #vim `

The MacBook Pro G4 from 2005 had 6 ports on the right side. Modern MacBook Pro have two Thunderbolt 3/4 with USB-C slots + one SD-Card reader.

mine is an integrated development environment for Coalton and Common Lisp for Windows, macOS, and Linux. #lisp

How LLMs Actually Work. FWIW.

TIL that there’s something like Astral uv for Chicken Scheme: Why I chose Rust for Basket. #scheme

The idea of “iterate over an entire collection” is a pretty common one in programming. For the sake of brevity, I’m not going to justify why I think this is important. But let’s look at a couple examples of where Scheme fails because it doesn’t have some generic way to operate over different collections. — Reflecting on Transducers

Exposing Floating Point. All of Bartosz Ciechanowski’s blog post are enlightening!

Networking changes coming in macOS 27: I guess I just need to back my (very) old Time Capsule to an SSD device. #apple

/me is listeniong to “Angel” by Massive Attack

R is not properly tail-recursive. True at present. May be unavoidable since the language provides access to the stack via things like sys.parent, but as it is rare to look at anything other than the immediate calling environment and call (outside of a debugging context) it may be possible to change that. — R and Scheme