p_l

7 ms·

91.
by p_l 2mo ago
EV7 were introduced after customers refused to upgrade to Integrity over crap performance.
92.
by p_l 2mo ago
Itanium was essentially (incompatible) PA-RISC 3 - it originated as HP project and the direction to totally replace HPPA with Itanium was there from the start. Non-Stop got ported early on because they needed some hardware and clients were
93.
by p_l 2mo ago
Alpha cancellation happened before HP/Compaq merger, when it was purely Compaq decision. At the time some partnerships were slowly reducing the base costs of making Alpha machines (with K7 Athlon motherboards and EV6 Alpha being essent
94.
by p_l 2mo ago
"fortunately" we can load swc compiled to wasm to deal with that.
95.
by p_l 2mo ago
Essentially, it's a case of smaller device with less powerful CPU and less powerful routing offloads, but which happens to have a hardware offload for the specific use case that they needed offloading - PPPoE. As the article itself men
96.
by p_l 2mo ago
Atos has a history with Universal Credit, IIRC. Admittedly the one time I felt pity for Atos, given that the orders to screw things up came from the client (government)
97.
by p_l 2mo ago
No, the half-bridge is less capable for various functions, but happens to have hardware PPPoE offload which makes it faster for this specific function but not for others
98.
by p_l 2mo ago
Batch job control is handled by alternative systems (already often triggering the work on mainframes anyway) like Control-M CICS is the big issue but AFAIK there were attempts. Everything else, including sort and VSAM, has various options p
99.
by p_l 2mo ago
Windows 3.0 becoming a hit was something unplanned by Microsoft originally - even the NT team was working with the assumption of using OS/2 API for applications. Win3.0 started out as skunkworks project initially hiding from management
100.
by p_l 2mo ago
MS-DOS truly beat CP/M-86 when it extended the APIs and features in PC/MS-DOS 2.0 (heavily inspired by Xenix), like hierarchical file system. From then on, applications would target MS-DOS in addition to the curse of being too IBM
101.
by p_l 2mo ago
Ah, with how cmucl was problematic to get running I never delved that deep. It indeed is not present in SBCL. That said, as mentioned, it gave no real impact on bootstrappability nor portability
102.
by p_l 2mo ago
Behold! https://www.lambda-symbolics.com/autolith Not mine, but interesting.
103.
by p_l 2mo ago
The sane bootstrap is not about porting to new architecture, but about building the compiler from source in the first place. CMU CL effectively requires that you use the same version of CMU CL to build it, IIRC, which in practice meant you
104.
by p_l 2mo ago
Part of why SBCL took longer is, IIRC, that SBCL went with embedding proper SEH support into generated code (important among other things to get page fault information), whereas CCL used VEH (which is simpler to use but only available from
105.
by p_l 2mo ago
I believe the real issue is that Scheme, which was (through university) often the first and last contact of people with Lisp family languages, has greatly exaggerated case of "everyone reinventing the wheel", and that's befor
106.
by p_l 2mo ago
There's another wordplay in the name. Namely, that "SB" stands for "Sanely Bootstrappable" - something that the CMU Common Lisp was unable to do
107.
by p_l 3mo ago
The quote I've seen was that Yu Deng dedicated part of his success to reading yuri (lesbian themed) manga.
108.
by p_l 3mo ago
Automated (semi)intentional lying on internet predates LLMs
109.
by p_l 3mo ago
Arguably this might reduce it, because now ROCm won't be prioritised for the GCN-based systems?
110.
by p_l 3mo ago
I have actually cooked with LLMs, specifically Gemini, few times this year. Works surprisingly well, can even tell it "I have so and so ingredients in my pantry, I want a keto-friendly meal, what can I make?" followed with some na
111.
by p_l 3mo ago
Windows 3.x could (and defaulted to where possible) to running in "386 enhanced" mode which actually used protected mode, IIRC. The problem was that the Win16 part ran all in one address space, and the separation support was mainl
112.
by p_l 3mo ago
Fun! in Dwarf Fortress way :) Thanks for the deeper dive
113.
by p_l 3mo ago
It was an early AVX-512 unit that resulted in down lock when you used more than a few instructions in short time, as well as resulted in a Linus rant. Later CPUs (updated skylake xeons and later, AMD Zen 4 and newer) don't have the iss
114.
by p_l 3mo ago
Will they remain bleeding edge by the time they are operational?
115.
by p_l 3mo ago
Kubernetes vastly reduced complexity of running things for me, in part because it sets common patterns, upon which further very usable patterns grow (like the various operators). At this point, I have a 64GB server on Hetzner that has decla
116.
by p_l 3mo ago
It made it trivial for me to deploy reproducible blocks that are also nicely integrated and automated on certain axes (DNS, LetsEncrypt, load balancer / reverse proxy, storage management, PostgreSQL databases with backups). All of that
117.
by p_l 3mo ago
TSMC also AFAIK is forbidden from setting up bleeding-edge fabs outside of Taiwan?
118.
by p_l 3mo ago
The funniest thing is that DSKY was, IIRC, a "temporary solution" that became the norm, and despite all the platitudes today it was apparently hated by astronauts.
119.
by p_l 3mo ago
That's how Windows handles it - the OS libraries are language runtime agnostic and do not export language specific symbols nor need them, and language runtimes are distributed often separately. So your C stdlib does not have dlopen() (
120.
by p_l 3mo ago
General consensus is that neither the model nor its outputs can be protected IP

More ›