the key point is that matrix transpose serves as a prime example of the > problem which appears trivial but nevertheless requires tremendous effort to > be solved efficiently for CPU. Root causes of this unpleasant surprise can be > traced to high memory latency and limited parallelization capabilities of > CPUs. Neither of these issues is going to be alleviated in the future. — What it takes to transpose a matrix

Migrating from Go to Rust.

Over the past few years, it seems like the rate at which new CLI tools are > being written has picked back up again, accelerating after seeing relatively > little activity between ~1995 and ~2015. — The Modern CLI Renaissance

/me is listening to “They Say in Love” by The Tempers

I’m not against writing code with debuggability in mind, but implicit returns are an idiom in Rust. It feels so unnecessary to reduce the idiomatical > adherence of the code due to a DAP gap, especially when the debugger on the > other side of DAP supports logging return values. Just don’t make me do this. > — Debugging Rust with Vim’s Termdebug

vim and the quickfix list: jump to a location, search and replace in multiple files, and other shenanigans: One of the best blog post about the underrated Quickfix list that I use all the time. #vim

Roswell is advertised as a solution, but it’s possibly the most un-Lispy tool in the ecosystem. It doesn’t download dependencies, or help you build them. — Deploying Common Lisp Scripts

Engineering Design Optimization, by Joaquim R. R. A. Martins and Andrew Ning.