amszmidt

14 ms·

151.
by amszmidt 2y ago
I don’t see how Nix is close to your dream, Nix is just like any other system and links things like any other system.. I.e. mostly avoids static linking. Debian did the strongest push for reproducible builds, and is 100% source available.
152.
by amszmidt 2y ago
That is a very, very tiny subset of things that are installed on any GNU or BSD system, and that need to get security fixes. Just recall the xz/sshd/system debacle, to patch your system all you needed was to replace libxz /
153.
by amszmidt 2y ago
The aversion to static linkage predates that, back many years static linkage also had other issues that have been solved today (ALSR ..). Many of the very basic points that Ulrich Drepper made some odd 20 years back ( https://akk
154.
by amszmidt 2y ago
Not to my knowledge. But consider something like crypto, libssl ... which is linked to almost everything, or libxz, zlib, etc. If there is a bug in a shared library, one can replace it with a interm one very easily, and the whole operatin
155.
by amszmidt 2y ago
They aren’t being rebuilt with that kind of frequency as you might think. They get rebuilt when a change in the package is made, not when a change in a dependency is made — which is a huge difference. There are plenty of packages that might
156.
by amszmidt 2y ago
Debian has about 59000 packages. Even rebuilding 1k of that is a significant pain on build infrastructure, specially in one go, if say a vulnerable library is found. You also now get a huge set of users who will now download these 1k of up
157.
by amszmidt 2y ago
And if you have two files with the same name...
158.
by amszmidt 2y ago
Alas there are two schools -- those that consider Lisp to be a language with its cradle defined by JMC's "Recursive Functions of Symbolic Expressions and Their Computation by Machine" and descendants thereof (Lisp1.5, MACLISP
159.
by amszmidt 2y ago
The left pinky finger would not have been used for hitting left Control in Emacs back then, rather one would have used the left _thumb_; the Control key was positioned beside the space bar on both sides. To use the left pinky on those keybo
160.
by amszmidt 2y ago
I don't see how quoting random articles proves either or, specially when it comes to specific jargon in a sport or even the original topic here wrt. engine vs. motor. > This article gives an outline of Formula One engines, also call
161.
by amszmidt 2y ago
The word “siłownia” could be directly translated to power plant though, -ownia is being a suffix for places / plants.
162.
by amszmidt 2y ago
That seems more like a typo than anything, in Formula jargon the engine is called a "power unit" not plant, not to mention that that a plant is generally a place of industry and not a object (e.g., nuclear plant ...). In either ca
163.
by amszmidt 2y ago
As someone fluent in both English and Polish (being my native language), I cannot see how silnik and a fixed place where power is generated, specifically connected to a network where that power is put out (i.e. powerplant) have anything in
164.
by amszmidt 2y ago
To call these Lisp Machine features is to skip quite a bit of history :-) RMAIL, info, etc predate Lisp Machines (ZMacs and EINE have their roots in ITS/TECO Emacs) by quite a bit. They where standard on ITS long before the Lisp Machi
165.
by amszmidt 2y ago
Power plant would be elektrownia. The suffix -nik is a common one that one can append to almost any noun to indicate that something or someone doing something, e.g. robot, robotnik (worker). So silnik translates to motor/engine, not
166.
by amszmidt 2y ago
Ah! The .plan file that finger(1) used reinvented for the Web world.
167.
by amszmidt 2y ago
The one about not using 'switch' and instead using combined logical comparisons is terrible ... quite opinionated, but that is usually the case with these type of style guides.
168.
by amszmidt 2y ago
There is the concept of "Fair Dealing" ( https://www.gov.uk/guidance/exceptions-to-copyright#fair-dea... ) which is similar to "fair use".
169.
by amszmidt 3y ago
The FSF copyright assignment isn't mandatory at all, and has never been. Many GNU projects use it, many don't. The copyright assignment also has wording to the extent that the FSF cannot just relicense things under a non-free so
170.
by amszmidt 3y ago
That assumes the maintainer wants to be paid. There are plenty of us who maintain FLOSS projects that do it for other reasons and any monetary exchange would burden us, since it might pressure one that this is now a job and you have to exe
171.
by amszmidt 3y ago
Works cloning though.
172.
by amszmidt 3y ago
The K-Machine would be a super interesting retro-computing project to get going. The schematics, the Lisp Machine system associated for it, are available (I'm unsure of legal status). If anyone is interested in driving that, I'
173.
by amszmidt 3y ago
I'm quite familiar, I've restored and written simulators and implemented FPGAs for almost all of them in various states of disarray. Your claim was that they had special architecture optimisations, that was not the case, and a co
174.
by amszmidt 3y ago
There was nothing "prototype" or "throwaway" about the CADR, it was heavily used at the AI lab for over 10 years, with both the Lambda and 3600 heavily based on it, to the point that the Lambda was microcode source and L
175.
by amszmidt 3y ago
That was really not the case, there are many misconceptions about the architecture of the Lisp Machine. The CADR for example is a very simple machine, and has no knowledge of OO or methods, likewise for the Lisp Machine macrocode.
176.
by amszmidt 3y ago
That is eliding quite a bit of the actual quote, “from one function into another,”. The goto being spoken about here is the unconstrained type that allows for both modification of jump location during run time and jumping in the whole addre
177.
by amszmidt 3y ago
One of the initial reason for the Lisp Machine project back then was to run Macsyma, since the PDP-10 was too constrained, and a multi-user system that meant you had to share resources. So MACSYMA runs well on the CADR :-)
178.
by amszmidt 3y ago
Everything is on the LM-3 project web site ( https://tumbleweed.nu/lm-3 ). :-) The current HDL implementation though only works on a unobtanium FPGA board. We are slowly working on porting it over to something that can actua
179.
by amszmidt 3y ago
A full GC took several tens of minutes… it was considered a coffee break type of thing. It is hard to say why it took that long to compile from the video, I’m guessing some network access to something …
180.
by amszmidt 3y ago
This is not an “early” CADR, it is just a CADR. By ‘81 they were heavily used at the AI lab and as gumby mentions, they aren’t fragile little machines. No running (real) CADRs exist, unless you consider the two FPGAs on my desk. For a CADR

More ›