I remember watching HN and seeing every time there was something Rust related trending, there was ALWAYS a post made shortly after trying to hype Zig and this went on for like 4 years.
Oh, please...if you haven't noticed the carpet bombing of rust advocacy on HN for more than 4 years and still in progress, you're deliberately not paying attention.
Yes...I remember the model 80. The cards you're talking about are 1) a design choice IBM made to use MCA as the official way to expand memory in the machine and not something any PCI bus machine I'm aware of followed, and 2) used the same generation memory as the planar memory. I don't think you're talking apples to oranges. YMMV.
I'm not sure where 'pedantic', especially when coupled with 'contributes nothing to the discussion', wasn't worthy of a downvote (which I didn't give), but I'm sure there's a "well, ackshually..." rationale there someplace.
That's not surprising. At the speed DDR4 runs, PCB design has to account for all sorts of weird effects. Adding the additional traces on the adapter probably pushes all sorts of timing over acceptable thresholds. There's a reason one of the big textbooks in the area is subtitled "A Handbook of Black Magic". [1]
I would counter tho that 1) this isn't the first time there's been a memory price/supply crunch, and "I've got a drawer full of last gen memory I can't use" is kinduva IT cliche, and 2) 'more memory' has always been a pain point, especially with industry practices like chipsets only supporting relatively small physical memory relative to address space (e.g. all those Intel LGA775 chipsets that capped at 4 or 8GB). Oh, and 2a) 'faster disk' has always been a pain point...
But, yeah...obviously my impression of things doesn't match market reality.
I dunno...I can envision something vibecoded prioritizing passing test suites producing something that does that, but isn't even functional in real-world production. Sort of like in the pre-AI world, where someone claims 'standards compliance' by way of passing compliance test suites, but can't actually interoperate well with other implementations of the standard. YMMV.
I have always wondered why there was never a big market[1] for "cheap PCI/PCI-X/PCI-e card you can stick a boatload of your old/surplus/n-generation old simms/dimms on and use as swap/slow memory/ram disk/etc". It's rare you can populate a motherboard with a full address space full of 'new' memory, and you can teach kernels to prefer some memory to others because of speed[2], so it seems like a no-brainer.
I seem to remember the market for doing similar with flash got neutered over patent issues, but I can't recall the details. And flash cache did end up being a market, at least for bigger players. Maybe something similar happened here, or maybe it just hit a niche I cared about at the time?
[1] I know there were a handful of products in this space, but my impression is they never really took off. I could be wrong.
[2] Definitely can in NetBSD; I've done it for archs like VMEbus where it's common to have a small, fast on board memory and much slower, often larger memory out on the bus. I assume this sort of thing is enabled in Linux by the work to support NUMA, but I've never looked into it.
Or, you could look at your peer answers where people very much do provide a non hand-wave answers. Chip fabrication isn't undergrad philosophy; there are well understood reasons for why things are done if you care to find and understand them. And there are stakes in the millions or billions of US$ for getting them wrong.
I run conceptually the same thing, but on FreeBSD instead of Debian. Different set of trade offs; not per se better or worse, just different, and in the end works just as well.
That does sound a bit agressive. To be clear, South Korea doesn't so much 'claim the entirety of the Korean Peninsula' as much as it aims to unify the entire peninsula into a single country through peaceful means (at least, since the military government left power in the late '80s).
This article is also from 2021 and things have changed a bit in the North. North Korea changed their constitution a couple of years ago and removed any mention of unification with the South, and defined their territory as basically the existing North/South split (aka 38th parallel). South Korea has been redefined from 'partner in national unity' to 'enemy to be destroyed, by nuclear weapons if need be'.
There's a lot of pretty interesting analysis of North Korea at the 38 North blog (https://www.38north.org/), among other good sources.
Yeah...using anything other than an Apple Approved(tm) scsi disk (or, really, anything 'not Apple') was an adventure. One of my least favorite Unixen, frankly. SVR2 based when most of the world on the AT&T side of Unix was SVR3 (and SVR4 was just around the corner), some BSD bits tossed into the blender, coated in a not-very-good MacOS emulation layer. Congrats to you on your perseverance; I recall the TCP/IP stack was...challenging.
A/UX was created so Apple could bid on government contracts that had a "must be Unix and/or POSIX" checkbox (common requirement at the time). IMO, they should have either gone all-in on a "MacOS apps running perfect on a Unix kernel" and picked a better kernel, or done the Atari thing and tossed the legacy OS and gone all in on a "Unix on Apple hardware". Instead it was 'meh' all around.
It's on a public IP, but isn't open to public users. I don't personally think 'the place I scribble stuff I want to remember down the road' is a blog, but I'm equally uninterested in arguing a distinction I don't think much matters. I don't know what you mean by 'extra step' unless you mean 'loging in', which is a hurdle I assume I'd have to jump over if I was posting a blog entry.
I have a wiki for that, but I keep reading the Arbiters of the Internet around here claim wikis are even deader than personal blogs, so what do I know. :-)
It's been a long time, but I'm pretty sure A/UX didn't use any of the toolbox roms and had it's own drivers (we had the source). A/UX booted from a MacOS partition because the Mac bootloader only understood booting MacOS (and it wasn't writeable with new boot code), so you booted to MacOS, then started SASH, which loaded Unix.
Also, swapping through 26 floppies to install would have been... Something.
We installed it from a QIC tape when it wasn't delivered on a SCSI hard drive. Not sure if that option was generally available tho; we were doing kernel development.
Oh, please...if you haven't noticed the carpet bombing of rust advocacy on HN for more than 4 years and still in progress, you're deliberately not paying attention.