People did know how to implement things back then, and TeX is a great example of that. It is just our definitions have changed over the years of what we consider better.

https://sv.wikipedia.org/wiki/V%C3%A5r_i_Sverige

The definition would certainly work in English countries, seeing it is just 0 to 10 degrees Celsius average over the course of a week (and after 15th of February).

There is (in general) no expectation of privacy in public in Europe. How you can use the material though, is a different matter ...

File names or directories starting with a comma where considered “junk”, and ones with a plus sign I think where considered “precious”.

To those downvoting, curious why? Many of the links are not viewable, since GitHub hides them, so any discussion becomes quite tricky.

I'm honestly quite confused what FFmpeg is objecting to here, if ILoveRockchip wrote code, under a compatible license (which Apache 2.0 is wrt. LGPLv2+ which FFmpeg is licensed under) -- then that seems perfectly fine.

The repository in question is of course gone. Is it that ILoveRockchip claims that they wrote code that was written FFmpeg? That is bad, and unrelated to any license terms, or license compatibility ... just outright plagiarism.

I suggest a careful reading of the GNU GPL, or the definition of Free Software, where this is carefully explained.

"The freedom to run the program as you wish, for any purpose (freedom 0)."

The informal also didn’t cloak their identity (implies some malicious intent), they simple did not use their work email. Nothing wrong with that.

Not exactly the above case, but from the GNU GPL version 3 (https://www.gnu.org/licenses/gpl-3.0.txt):

      13. Use with the GNU Affero General Public License.
    
      Notwithstanding any other provision of this License, you have
    permission to link or combine any covered work with a work licensed
    under version 3 of the GNU Affero General Public License into a single
    combined work, and to convey the resulting work.  The terms of this
    License will continue to apply to the part which is the covered work,
    but the special requirements of the GNU Affero General Public License,
    section 13, concerning interaction through a network will apply to the
    combination as such.

Has the decompiled version.

programs.

    ] Pointer Fields Now 25 Bits; Flag Bit Gone.

    Each typed data word in Lisp machine memory used to have one bit called the "flag bit" which was not considered part of the contents of the word. This is no longer so.  There is no longer a flag bit; instead, the pointer field

    This extra bit extends the range of integers that can be represented without allocation of storage, and also extends the precision of small-floats by one bit.

    On the Lambda processor, the maximum size of virtual memory is doubled. This is the primary reason for the change.  Unfortunately, the CADR mapping hardware is not able to use the extra bit as an address bit, so the maximum virtual memory size on a CADR is unchanged.

    The functions %24-BIT-PLUS, %24-BIT-DIFFERENCE and %24-BIT-TIMES still produce only 24 bits of result.  If you wish to have a result the full size of the pointer field, however wide that is, you should use the functions %POINTER-DIFFERENCE and %POINTER-TIMES (the last is new), and %MAKE-POINTER-OFFSET with a first argument of DTP-FIX to do addition.

    The functions %FLOAT-DOUBLE, %DIVIDE-DOUBLE, %REMAINDER-DOUBLE and %MULTIPLY-FRACTIONS use the full width of the pointer field.

    The values returned by SXHASH have not changed!  They are always positive

    > If Stallman had started with a kernel, there would be very few people who had the legal right to run any utilities or apps on the new kernel