"Who art Henry?" was never grammatical English. "Art" was the second person singular present form of "to be" and it was already archaic by the 17th century. "Who is Henry?" would be fine.

In some languages you can put a second person conjugation next to a noun that might otherwise use third person verbs, and it serves as implying that you are that noun. I'm not sure if older forms of English had that construct. I think many Indo-European languages do.

The part of the lord's prayer that says "our father who art in heaven" is kinda like this - father is linked to a second person conjugation. You could remove some words and make it into "father art in heaven", which you claim is ungrammatical. I'm skeptical that it was.

“who art in heaven” is a grammatical relative clause because the subject of the verb is the relative pronoun “who” which is second person in that context. You can still get this kind of thing in modern English, for example “I, who am a farmer, will be happy” is grammatical because the relative pronoun “who” is first person there. That doesn’t mean it would be grammatical to say “*A farmer am happy” and it wouldn’t have worked with art either.

Conceivably it’s grammatical if Henry is vocative and the pronoun is dropped colloquially, like “Who art [thou], O Henry?” but it’s a stretch.

Who art thou?

(Well, not 19th century...)

The problem is the subjunctive mood of the word "art".

"Art thou" should be translated into modern English as "are you to be", and so works better with things (what are you going to be), or people who are alive, and have a future (who are you going to be?).

Those are probably the contexts you are thinking of.

Wherefore are you going to be Romeo?

Wherefore is closer to why, or (as taught in literature classes) for what reason. Wherefore is a question, therefore is an answer.

"Who is Henry?"

I gave it a try a few months ago. The first thing that I searched for was the REPL. Comparing it with Python, I prefer ipython over irb. It would be nice to see some improvement on DX on the REPL side

What actionable things do you think IRB is missing vs ipython?

Updated revision (2022): https://nlp.seas.harvard.edu/annotated-transformer/

I was about to mention that.

Wonder if Wails have the same issue on Linux.

Have you tried cocoindex?

[1] https://cocoindex.io/

[2] https://dev.to/cocoindex/how-to-build-index-with-text-embedd...

Can you elaborate on this? How is npm/cargo/etc better than pip on this regard?

As far as I know, files like requirements.txt, package.json, cargo.toml are intended to be used as a snapshot of the dependencies in your project.

In case you need to update dependency A that also affects dependency B and C, I am not sure how one tool is better than other.

Open a requirements.txt and a package.lock.json next to each other and compare. Then you will know the answer to the question what npm, cargo, and others are doing better than pip. Oh, did I sneek a ".lock" in there? Damn right I did.

They will resolve a version that works for all dependencies if it exists.

I gave it a try a few months ago, but did not work for me. My main issue is that atuin broke my workflow with fzf (If I remember correctly, pressing ctrl + r to lookup my shell history did not work well after installing atuin).

I'm sympathetic, also a longtime fzf user here. I install it reflexively on any system I use for more than a day or two.

This is configurable! I use atuin, but fzf with ctrl-r.

Another advantage of using Elixir/Erlang/Phoenix is high availability. If one client/incomming requests is taking a lot of time to complete, other users are not affected. We can even inspect the system in real time via iex. Please search for "The soul of Elixir" in YouTube, Sasa Juric explains this. Highly recommended.