On the internet, the origin is the server sending the response to the user. I suppose you can look at it from the perspective of the owner of the server -- from their frame of reference, their journey _starts_ when they receive, process, and respond to the request.
Granted, computer scientists are infamously known for being terrible at naming things.
Don't forget all the abbreviation. "超市", supermarket, is abbreviated from "超級", super, and "市場", market. The equivalent in English would be "sup-mark" or something along those lines. (Or in Japanese, just "super".)
Since we're now talking about verbal rather than written:
> No matter how fast or slow, how simple or complex, each language gravitated toward an average rate of 39.15 bits per second, they report today in Science Advances.
This tracks - it's difficult to speak at the same pace in Chinese as I can English. That said - are those 39.15 bits plaintext? Compressed? Encrypted?
The size of a word does not correlate with it's concept - I still posit that some languages can transfer concepts faster than others, minus our baud rate.
Edit: Or, perhaps I am not as gifted an English speaker as my bias has presumed :| For example, I had to lookup "syntagmatic".
We recently installed something similar (https://miniprofiler.com) into a legacy ASP.NET MVC app. It is setup to only be visible in local development environments.
In areas of the code where ORMs obscure the actual SQL that runs, it's shortened the amount of time and effort it takes to discover a slow route and optimize it.
"Handy to have that extra info in your dev environment" is pretty spot on.
Origin: The point at which something comes into existence or from which it derives or is derived.
How can the request's destination server be the origin, if it is the destination server?