Yes, I do not trust TM. That's why I have both a backup with TM for convenience and also to have all the files (including system files), and a mirror of the important files (basically my home directory) with `rsync`.
"(...) maybe growing vegetables or using a Haskell package for the first time, and being frustrated by how many annoying snags there were." Haha this is funny. Interesting reading.
I actually plan on doing this year in Gleam, because I did the last 5 years in Haskell and want to learn a new language this year. My solutions for last year are on github at https://github.com/WJWH/aoc2024 though, if you're interested.
This reminds me of Henri Laborit's book entitled "Eloge de la fuite" (in praise of flight) which states that when faced with stress, we can respond with action, flight, or inaction. Unlike the other two responses, inaction is toxic to the body. Maybe giving up corresponds to flight. I didn't read the article.
"fuite" is french which means to escape, to flee. Flight is only in context of planes or flying transportation.
As for the sense of it, you're right, it's either do something, go away, or do nothing.
(of a linguistic form) commonly used in an earlier time but rare in present-day usage except to suggest the older time, as in religious rituals or historical novels. Examples.
thou; wast; methinks; forsooth.
Its usage isn’t extinct, but it is far less common than it used to be and IS largely extinct in casual day to day speech. We would say flee, run away, escape, or any of a dozen other things more often than “flight”
Since my mother tongue is french, I guess I didn't choose the proper english word. In the context of an attack we sometimes see the "fight or flight" response. But I don't know what is the best term to translate "fuite" in this context.
"Flight" is used in English to mean "an act of fleeing". It's perhaps less common outside of specific idioms ("fight or flight" being one of them, yes), but people will generally understand you correctly in context. It seems from the rest of the comments that GP is also not a native English speaker.
I only read the first 88 pages of Prolog Programming in Depth but I found it to be the best introductory book for programming in Prolog because it presents down to earth examples of coding like e.g. reading a file, storing data. Most other books are mainly or only focused on the pure logic stuff of Prolog but when you program you need more.
Another way of getting stuff done would be to use another programming language with its standard library (with regex, networking, json, ...) and embed or call Prolog code for the pure logic stuff.
reply