Apple has low memory behaviour way better optimized than Windows, so running at 8GB will not be as painful as it is with windows - but in the background the OS will constantly shuffle stuff around to avoid running out of memory, which costs performance.
16GB is the bare minimum for computer nowadays - and that applies to macs as well. I'm currently using a 16GB air m1 for some things, and I also regularly run into performance issues due to memory limits without doing heavy stuff.
A small form factor, small high density connector. Most interfaces are not populated, as on the regular pis, but just lead out via the connector, so you can decide what you want to expose on your compute module carrier. It has a gbit ethernet chip on board, and a pcie chip - rpi4 also has pcie, but it is hooked up to USB3 there. With the compute module you can decide what you want to do with that.
A good starting point for a wikipedia rabbit hole covering the software aspects on how to drive a display: https://en.wikipedia.org/wiki/XFree86_Modeline
50 pin centronics should be bulkier in all dimensions
The real danger is when people start believing the artist more because of how much more aesthetically pleasing they can make their misunderstandings, and trust me it is a real danger.
We already have that a lot in our field - people just buy a shiny UI, and don't care about the rest.
One of the first times I've encountered that was when a customer bought a ridiculously overpriced firewall box because of the easy to use GUI, and asked me to implement a pretty complex rule set. The irony of having bought the fancy UI so the can do it themselves, and then hire an expert to do it instead was completely lost on them.
This thing had troubles doing what was needed there, and had pretty much zero debug functionality exposed - so eventually I suggested they give me one of their old desktops and half a day to see if I can get the ruleset done the old fashioned way with OpenBSDs pf (that was before Linux kernel 2.4 was released, so Linux firewalls couldn't do stateful filtering yet, which was required there) - got everything running in a morning, they decided to just stick with it, and the expensive fancy box was collecting dust.
I guess it depends on how you are using your phone. If you're mostly using it between charges (possibly replacing other devices) it indeed doesn't matter. If you care about standby time, or use it as music player or similar tasks more than active use it does matter.
You mentioned a pull request, and that it got edited - which in my workflow is pulling the commit and amending it.
A well proven clbuttic solution.
Ah, seems I missed a "on GOG" in the reply.
I like how you have a home smartcard. I can’t believe many do.
Pretty much anyone should do. There's no excuse to at least keep your personal PGP keys in some USB dongle. I personally wouldn't recommend yubikey for various reasons, but there are a lot more options nowadays. Most of those vendors also now have HSM options which are reasonably priced and scale well enough for small hosting purposes.
I started a long time ago with empty smartcards and a custom card applet - back then it was quite complicated to find empty smartcards as a private customer. By now I've also switched to readily available modules.
Why do you think cloud operators are lying?
One of the key concepts of the cloud is that your VMs are not tied to physical hardware. Which in turn means the key storage also isn't - which means extraction of keys is possible. Now they'll tell you some nonsense how they utilize cryptography to make it secure - but you can't beat "key extraction is not possible at all".
For the other bits I've mentioned a few times side channel attacks. Then there's AMDs encrypted memory (SEV) claiming to fully isolate VMs from each other, with multiple published attacks. And we have AMDs PSP and intels ME, both with multiple published attacks. I think there also was a published attack against the key storage I described above, but I don't remember the name.
I agree that our stuff is unlikely to be victim of an targeted attack in the cloud - but could be impacted by a targeted attack on something sharing bare metal with you. Or somebody just managed to perfect one of the currently possible attacks to run them larger scale for data collection - in all cases you're unlikely to be properly informed about the data loss.
Not enough onions. Your average mettigel has better mett/onion ratio.
With lower voltage DC you can only set the house on fire. With high voltage AC you can set the house on fire and electrocute people. In a safety oriented company you'd try to limit the parts of the device carrying 230V (or, more generally: if your device has dangerous bits, you try to keep those bits in as few places as possible, as that limits teh amount of places you need to keep safe). Now obviously this has limits - like the mentioned bed size - but I don't think we're yet at a point where this should overrule safe design principles.
I haven't seen a bambu printer myself yet - but given that the cable is undersized and not protected against side effects from bed movement I'd bet they also skimped on on making everything carrying 230V safe - in which case this is a cheaper design. I'm reasonably confident that a safe 230V heating design for a printer that size would not give you noticeably cost savings over a DC design, if at all.