HN user

amszmidt

352 karma

sauerpunk gnu hacker / software freedom or bust / wizard of zymurgy / lisp machine revolutionary

Posts0
Comments185
View on HN
No posts found.
Roman Letters 2 months ago

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.

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.

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.

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.

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.

MIT System 99 was made after the first LMI release, which was based on MIT System 98 (and even slightly older releases) - which removed the flag bit. See the release notes here https://tumbleweed.nu/lm-3/sys-msg/sys98-msg.html

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
of the word is one bit larger, making it 25 bits in all.
    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
fixnums less than 2*23.
    > 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
That is really not true, one of the most important things when it comes to the GNU project and the whole Free Software movement is the ability to run _any_ program, be it non-free software or free software. This has been parroted for more than 40 years now ...
    Note however, that you can't use diff on binaries, [...]
You absolutely can, but you need to use an external diff tool:
   fossil diff --command "compare"
You can also customise the diff-command variable. You might need to pass --diff-binary .. I forgot.

As for storing binaries, unversioned files have no history, and are not synced automatically.

The original cc was just a wrapper like this Python example around a bunch of external programs, calling c00, c01, until something could be fed to as and then linked using ld.

GCC does basically the same thing even today,

A carriage is a wagon that transports people, not "things", a carriage are also usually wheeled, just like wagons.

In this case, one reason why "wagon return" might have made more sense is because there is a wagon that holds the platen of the typewriter.