Not to mention I bent all the pins on my Cyrix MII ttying to get it in that stupid socket.

I understand pre-OS X Macintoshes used colons.

I guess the assumption is more that for me, a fresh install is often about decluttering as much as anything-- the five Wayland compositors, three music players, and six pseudo-IDEs I tried and didn’t like don’t need to follow me to the next build.

In a conventional install, that just means “don’t check the checkbox in the installer next time”. In a Nix-style system, this is a conscious process of actively deciding to remove things from the stored configuration, no?

I suppose the closest I’ve gotten was recently migrating my setup from a desktop to a new laptop. Mostly copying over some config from my home directory, but even then, I wanted enough different stuff-- removing tools I don’t use on the laptop, adding things like battery monitoring and Wi-Fi control-- that it involved some reconfiguration.

I suspect the tooling isn’t quite there yet for desktop use cases.

If I were to try to replicate my current desktop in an immutable model, it would involve a lot of manual labour in scripting or checkpointing every time I installed or configured something, to save a few hours of labour in 2 years time when I get a new drive or do a full install.

The case is easier for defined workload servers and dev environments that are regularly spun up fresh.

No, this is a general practice-- I see it a lot with third-party vendors who want you to integrate with their services. They’ll expire the documentation portal password after 90 days, but the actual user facing service still accepts the same “password123” that’s been set since 2004.

I suspect the pattern is to protect the vendors from developer scrutiny: by the time you’ve jumped through enough hoops to read the docs and realize it’s trash, the execs have signed the contracts and the sunk costs are too high to bail out.

Also add another 6 months to actually get the credentials for the test environment.

ARM was designed because the 6502 was approaching end of viability, and Acorn (the maker of the BBC Microcomputer) needed a next-gen product. At the time, RISC was the trendy thing, and I suspect the 286 and 68000 were too expensive to adapt for their products; they weren’t pushing £5000+ workstations like IBM or Unix vendors.

It was light and small because they had a small team; low power was a happy accident.

I have a similar one, different seller and possibly submodel, but also a refurb HGST 12T enterprise drive. It sounds like I left a soda on my desk most of the time, subtly popping and ticking.

This is the firmware I’ve been working on. Basically I wrote it because at the time (early 2023) there wasn’t a “good” keyboard firmware like QMK or ZMK for the CH32V305. Now it supports keyboards, joysticks, and a rudimentary pointing device made out of a PS2-style analogue stick.

https://gitlab.com/hakfoo1/ch32v-keyboard/-/tree/fightstick?ref_type=heads

That branch has the mapping I used. Note this firmware has a keyboard-centric assumption that switches are wired as a matrix (between two sense lines), even if that matrix is 1x24, rather than just grounding a sense line individually.

The stick portion was one of those “Pandora Box” devices that was built into a cabinet and pre-wired to a crappy Android TV box.

I bought it because I figured it was probably cheaper than cutting a decent looking cabinet and buying the buttons off AliExpress. That also meant it came with a predefined cable harness to fit the Android box. In the hopes of making it tidy, and reversible, I ordered a little throwaway PCB that accepted the existing 40-pin plug and bridged it to a nanoCH32V305 breakout board. Of course, I made a design mistake, so the PCB had bodge wires, so not much was saved.

If you’re starting from scratch, you could direct-wire to the MCU breakout board.

I’m thinking it might be my 2.5G router when it drops. Or worst case, maybe retire the Atom I’m using for a NAS.

I’ve been using some much smaller CH32V305 based keyboard controllers for a while, recently built a fightstick aroubd the platform. Now if only I fidn’t suck at joystick games, having grown up on gamepads.

Some of them have poor stability. I gave up on a Sound Blaster Audigy RX after it caused random crashes on two different Socket AM4 mainboards. I just got a 10 metre optical cable and a cheap DAC next to my reciever.

I suspect the industry is in a tailspin; the last players standing really don’t have to give a **** because the alternatives are onboard sudio or $$$$ pro cards.

If done right, it could be a positive curator. Rules like “any drivers you get off of Windows update met certain tests, are not padded with unrelated crapware, etc.”

But I suspect that won’t fly. My main experience with WU drivers is a tendency to replace new drivers with old, broken ones. And I doubt printer makers-- the guys who made a 600MB driver to do the same tasks that a LaserJet 4 did with a 30k driver 30 years ago-- would play ball.

I guess I’m the only one who LIKES the latching plug.

The less economic and tech dependencies China has on the West, the more free they are to act on their own accord.

The US is concerned about Taiwan-- they wrote a blank cheque of support because it was a DeMoCrAcY back when China was a far weaker economy and military, and it will now be very difficult and expensive to stop reunification. Using TSMC as a shield is no doubt part of policy-- “invade and we blow the tech world back to 2010” is a viable threat until other countries get 7/5/3nm.

But their fear is more general; they are losing their economic and geopolitical dominance, and one of their big bulwarks-- advanced tech-- is giving way. They’re trying to hype up the fear and concern. Expect a lot more sabre rattling by the West.

I’m curious if we have a detailed historic analysis of the origin of the term.

I always figured it came form the “rice burner” mocking for Japanese motorbikes and cars. I figured this was mostly a pick about their relatively low performance. Aside from the “Asians eat rice” source material, is that intended as an insult to Asians in general, or more directed to the design committees at Toyota and Honda-- that they couldn’t design a car capable of burning petrol?

To try a parallel concept: If an x86-64 enthusiast made fun of an ARM chip by saying it was “manufactured on a crumpet substrate” would that be an insult against the British, or more using that it comes from a British firm to provide vocabulary for a product-related insult?

OTOH, I never really saw the term widely used to describe a desktop configuration before here, and it feels weird because of that more than anything else. I’m trying to remember if it was seen in the “PC Case Mod” community circa 2000, because they actually used a fair number of techniques and ideas from the car tuning scene that also used the “ricing” term (lots of cold-cathode lighting and weird 12v accessories)

If only they’d offer a sanctioned Linux client.

I still reboot for my Qiqi fix. She’s adorable and versatile.

If Opera had stayed in its lane, it would be pretty much Vivaldi.

I wonder if one of the things that tends to get filtered out in preservation is proportion.

When we willfully save things, it may be either representative specimens, or rarities chosen explicitly because they’re rare or “special”. However, in the end, we end up with a sample that no longer represents the original material.

Coin collections disproportionately contain rare dates. Weird and unsuccessful locomotives clutter railway museums. I expect that historians reading email archives in 2250 will see a far lower spam proportion than actually existed.

I’m surprised that chipmakers waited this long. I have the feeling they all treat their firmware divisions as a necessary evil.

Has there ever been positive news associated with the lowest levels of firmware, or is it at best begrudging “AGESA 4.2.0.0 finally fixed the issue where the memory is clocked down to 250MHz when there are two runners on base” fix notices.

If they can toss the problem on a bunch of enthusiasts and people willing to finance open-source developers, they get it our of their hair and earn some public praise.

Realistically, it might be interesting for long-term platform support-- if someone wants to keep tweaking and optimizing a 10-year-old platform, they’ll have more tools at their disposal to do so.