ruricolist

"If you have an active subscription, Translate still works."

If you're actually planning on reading any of the essay, "The Poisoned Chalice" is the section most likely to be of interest to this audience, especially this bit:

> Big AI essen­tially uses its tech customers as an R&D facility. Big AI licenses models to these compa­nies. Tech compa­nies compete to adapt their busi­nesses to AI. Once a concept is proven, Big AI directly takes over that market. The labor-replace­ment story will grow into a company-replace­ment story.

The sketch here would be that Lisps used to be exceptionally resource-intensive, allowing closer-to-metal languages to proliferate and become the default. But nowadays even Common Lisp is a simple and lightweight language next to say Python or C++. Still it's hard to overcome the inertia of the past's massive investments in education in less abstraction-friendly languages.

I'll mention the recent Second Act as an excellent survey of the phenomenon of the late bloomer: https://www.henry-oliver.co.uk/home.

Tim Cain on YouTube has been posting some technical details of the original Fallout implementation.

If you just do C-x C-f, M-n to get the "next completion" gives you the file at point.

"Over time, this shaped a deep biological aversion to unnecessary exertion." This is both ahistorical - dancing and athletic competition are effectively human universals - and abiological - wild animals play.

For forcing colorized output: I personally prefer pipetty (from the colorized-logs package on Debian) to unbuffer, since unbuffer merges stdout and stdin.

I'd replace the underlying data structure used to represent buffers (https://www.gnu.org/software/emacs/manual/html_node/elisp/Bu...) with something more sophisticated, like ropes or piece tables.

The Dark Reader browser extension works for HN.

The history here is that Common Lisp gets reduce from APL (https://aplwiki.com/wiki/Reduce). It's not an attempt an ML-style fold, but a different formalism from a different lineage.

It's true there's often a tenuous relationship between blurbs and books, but setting up reviews as the more reliable alternative to blurbs is untenable. Most reviews I read, especially in literary publications, have little to do with the book nominally under review. Mostly the book is there to provide the occasion for an essay, and the only part of the book that actually makes an appearance is the title.

Personally I feel about Scheme's distinction between false and the empty list the way Schemers feel about CL's distinction between variables and functions.

DDisasm ("a fast disassembler which is accurate enough for the resulting assembly code to be reassembled") uses Souffle: https://grammatech.github.io/prj/ddisasm/

Resolve is another tree-sitter based tool that does this:

https://github.com/grammatech/resolve

I have a project to do that, https://github.com/ruricolist/vernacular, although I'm not working on it right now.

The CL convention would be to have a function called bar that converts whatever its argument into an instance of bar. Make it generic and new libraries can easily add their own conversions for their own data types.

Related, for C++: https://cpp-rust-assisted-migration.gitlab.io

There is a fair amount of academic work on bidirectional tree transformation with lenses, e.g. <https://www.cs.cornell.edu/~jnfoster/papers/lenses.pdf>. It breaks down to proving three operations (Get, Put, Create) that observe three laws (called GetPut, PutGet, and CreateGet); these give you bidirectional transformations you can compose arbitrarily. Later work introduces concepts like "quotienting" (for when you actually want the transformation to be lossy in certain ways) or "discerning" (non-total) lenses.

I hated the spring-loaded spouts until I learned the trick: you have to actuate them once to release gas before you actually starting pouring. Haven't spilled a drop since.

That novella sounds fun.

I mean distinguishing between `null`, `false`, and `[]` on the JSON side. Most JSON libraries for CL by default parse them all as `nil`. (ST-JSON excepted.)

I like the way CL does things but it makes dealing with JSON occasionally annoying.

Mongols.

Contrary data point: I watch a lot of classical music on YouTube and it gives me consistently excellent recommendations.

(Although I only take recommendations from the front page, and ignore the playlists entirely.)

It's not obvious from the name, but magit-log-buffer-file also lets you browse the history of just the current region.

Ripgrep?

Regional indicator symbols:

https://en.wikipedia.org/wiki/Regional_Indicator_Symbol

I suspect they're talking specifically about the longleaf ecosystem:

https://en.wikipedia.org/wiki/Longleaf_pine_ecosystem

What is question driven drafting?