insect VS unix-history-repo

Apparently this replaces https://github.com/sharkdp/insect

You might like https://insect.sh/ ;)

For the record I use insect.

https://github.com/sharkdp/insect seems to be somewhat similar, but it's mostly for physical units. However, it's the only opensource one that is embeddable.

Insect: https://github.com/sharkdp/insect

It is a bit slow but has decent features, including some physical units support.

I set up Tilda (or another Guake equivalent; I tried a bunch of them and can’t remember on which I settled in the end) to run it automatically when a terminal is opened, when pressing Scroll Lock. It’s quite neat: when I need to do a quick calculation, I just hit Scroll Lock, which spawns a drop down terminal with the focus; then type whatever I want to calculate; then control-D to dismiss the drop down terminal and I am back in whatever I was doing without moving either hand off the keyboard.

I do more or less the same thing on my Mac with Alfred.

I'm in the same boat and will pay for Kagi, though I have a different interaction with a search engine and thought you might like the counterpoint. Notably, I don't use Google for most of what you described:

Translation: I use DeepL instead (google is doing poorly on Asian languages)

Conversion: not having much need for imperial but I use this for all unit conversion (though usually directly in my terminal): https://insect.sh/

Wikipedia: if I type Wikipedia+something my browser automatically use the wiki engine (chrome can do that too)

Word definition: on OSX I long press on the trackpad and the definition pops up (across languages, translation too for single words)

Lyrics: Spotify show them now! (admittedly that's a recent feature)

insect.sh goes up to about 109 × 1015.

There is also https://github.com/dspinellis/unix-history-repo (Continuous Unix commit history from 1970 until today)

FWIW, ls in Research-V6 back in 1975 had 10 options. https://github.com/dspinellis/unix-history-repo/blob/Researc...

By BSD 3 in 1980 it had 11 options. https://github.com/dspinellis/unix-history-repo/blob/BSD-3-S...

The thing is, we can see even from the 1970s 'ls' how the Unix model doesn't meet the goal "to chain these simple programs together to create complex behaviors".

There is no option to escape or NUL terminate a filename, making it possible to construct a filename containing a newline which makes the output look like two file entries.

The option for that was added later.

There's also the issue that embedded terminal codes will be interpreted by the terminal.

This is what it looked like about 7-8 years earlier: https://github.com/dspinellis/unix-history-repo/blob/BSD-1/e...

RA92 (1989): 16 ms / 8.3 ms.

Note that the RL02 (and V7) and RA92 mentioned in the article are separated by about a decade.

[1] https://github.com/dspinellis/unix-history-repo/blob/Researc...

The earliest version I could find [1] is already written in C.

[1] https://github.com/dspinellis/unix-history-repo/blob/Researc...

Here's a 1997 citation for "top cpu processes." It's not as close to the original 1984 release as I would like, but it's better than Wikipedia. https://github.com/dspinellis/unix-history-repo/commit/aee34003d7964653c44c31f5bf6bcf136b32c4f3

> The “why” goes into the PR and more importantly, engineering documentation and inline comments

This just ensures that the “why” is lost when someone comes looking years later.

From experience, SCM metadata is far more durable than just about any other work product we produce. Five decades later and RCS commit info was still available for the Unix sources, and history could be reconstructed: https://github.com/dspinellis/unix-history-repo

I’ve used 35-year-old commit messages to help understand a long-standing issue, decades after all other related organization tooling and data had disappeared.

P.S. I remember I looked into early versions of C (they survived in Unix historic releases) and that, finally, revealed to me why C does something really stupid and conflates arrays and slices (pointers). Initially C had no arrays! Or, rather, what it called arrays were, actually, pointers. “Normal” arrays were added at some point, but because these weird slices/pointers were already there that caused endless confusion. It wasn't resolved before C became popular and after that it was too late. Go repeated that mistake with slices, of course.