Redshift is indeed a matter of speed. But due to the expansion of the universe, relative speed and distance are directly related (Hubble's law).
So farther away means faster relative speed and thus more redshifted (Doppler effect)
Farther away also means older light (due to the finite speed of light).
Putting that all together means that to observe old light from the start of the universe we have to look in the IR spectrum.
In the article it describes the N+1 problem with an example of the fossil timeline.
In a system using Postgres, you would select all the timeline entries and then generate one big query to get the details of all the timeline items in one sql request.
With sqlite you can just iterate over the items and do the queries separately.
This makes handling this scenario much simpler.
There are plenty of examples in this thread alone.
In my opinion hinting won't help. Everyone who cares about the performance gain will enable the hint (which I expect will be almost everyone) so you have won nothing but added noise with the hint.
There is indeed also a relation between momentum and (rest) energy describing the conservation of energy,
In the rest frame this relation reduces to the famous E=mc^2.
Because advent is a common term for the 4 weeks before Christmas even in non religious contexts. And that is how it's used in this non religious project.
Not quite, without MCAS the flight behavior is quite predictable, it just doesn't match the existing type certification and it falls outside of the allowed parameters for this class of planes.
One big area where taskwarrior shines compared to solutions like todo.txt or org mode is synchronizing between devices using taskd. Although it is a bit involved to set-up, once it works, it works very well.
I am slowly trying to add task identities to Simpletask to get closer to this ideal (at the cost of 'ugly' meta data in the Todo file)