amszmidt

“unless” is “if not” — it is not generally looping construct.

”unless” already existed in early Lisps in the 1970s…

I skimmed the standard and POSIX, but couldn’t find anything that an implementation is required to support FENV_ACCESS.

You take short fibers, and twist and splice them together to get longer fibers. And you repeat until you get the desired length, or thickness...

Lots of videos of how to make it on the Internets using nettle, or some other plant (flax is still used to make clothes today though through industry methods).

There are ways to predict a child’s height as an adult that are very accurate.

Most countries track growth curves, and ask parents about what their height is to correlate data with. One can also use bone age assessment.

Don’t think TeX ever did that, that was a “simple” Pascal program.

Lisp Machines though.. updating the operating system was by loading bunch of compiled files that replaced currently loaded functions in memory.

Then again, Lisp Machines where very proud of self modification — the CADR had a fun feature where it could modify the next instruction depending on things…

How the world has changed.

You need to go back a few more hundreds of years, hunk is an old term that just means "small piece of something larger".

It has been in common usage in computing since long before 1985 .. for a really interesting and obscure way hunk has been used:

https://www.maclisp.info/pitmanual/hunks.html

How cold is cold? :-)

Water below ”sea” level tends to stay around -1C (salt water) to 4C. Below that, water becomes ice…

Ambient temperature can drop to -40C … internally these ice blocks hoover around -10C.

Only because the X Window System is very heavily documented, e.g., in the excellent "The Definitive Guides to the X Window System Series".

The key here is “based on Portland cement”, which is generally has water repellent added to it making it water proof.

Normal cement, concrete .. Is a different story.

Would love to see some statistics on that.

It is also capable of doing it over the wire.

Fun fact. DIRED pre-dates EMACS.

DIRED on ITS is also similar enough to today’s DIRED.

But it is. There is a link to the original text at the bottom of the translation.

The details of lexical scope where defined in Algol 60 (1960), nearly 2 decades before Rabbit (1978).

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.

This a common thing shared with the Nordics. The English term would be “meteorological spring”.

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).

Would be nice if someone did it with Swedens laws too!

In Sweden, you're allowed to film/photograph in public without the need for any consent.

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

Not if it is an alias.

It was suggested by Tom Lord (RIP), who used it heavily long before he wrote GNU Arch.

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

Thanks for the link; sadly none of the links to the repo can be viewed to see what exactly occurred.

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

Incorporating compatible code, under different license is perfectly OK and each work can have different license, while the whole combined work is under the terms of another.

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 think maybe you're mixing up distribution and running a program, at least taking your initial comment into account, "if you train/run/use a model, it must be open source".

In the context of Free Software, yes. Freedom one is about the right to study a program.

That is not really correct, the GNU GPL doesn't have any terms whatsoever on how you can use, or modify the program to do things. You're free to make a GNU GPL program do anything (i.e., use).

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

Because it would violate freedom zero. Adding such terms to the GNU GPL would also mean that you can remove them, they would be considered "further restrictions" and can be removed (see section 7 of the GNU GPL version 3).

It isn't the difficult, a license that forbids how the program is used is a non-free software license.

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

An employee doesn’t act as an official representative of their employer nor do they speak for the employee in any official capacity. That is what the message says.

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

”No association” and “I am not a representative” are quite different things to say.

> Wait a sec. IANAL, but if I license something to you under the GPLv3, you may not license it to someone else under AGPLv3 or a commercial license.

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.