spatular

The trick is to redesign the bricks for worse tolerances. With 3D printers you can print very nuanced springy elements that are impossible to achieve with injection molding. I got some reasonable bricks years ago on cheap printers with PETG, should work even better now with modern printers and ABS.

There is also prompt processing that's compute-bound, and for agentic workflows it can matter more than tg, especially if the model is not of "thinking" type.

Yes, 140W sustained, 160W burst (~10 seconds).

Clickhouse is a network server, duckdb and polars are in-process databases. It's like postgres vs sqllite.

You can take a look at orange pi 5 plus. It has M.2 for WiFi and M.2 for SSD, both PCI-E. It's in $100+ category though.

Orange Pi 5, "plus" version also has 2gen 1-lane pci-e (M.2 wifi), and 3gen 4-lane pci-e (M.2 SSD) and 2x2.5Gbit ethernet.

8nm, pretty power efficient. I've measured it to run at 0.7A@5V idle and 1.2A@5V with all 8 cores loaded with md5sum /dev/zero; iirc it had 1 ethernet connected, no other periphery. Running on Armbian.

You'd need to spend at least 110kWh to convert CO2 back to propane, maybe much more. No matter what you do, LPG -> CO2 -> LPG cycle has to be energy-negative.

To be precise, that'd be called MPU -- memory protection unit.

MMU allows linux to provide a "flat" memory space to each userspace process. This memory space is assembled from 4KB pages that can be randomly dispersed throughout physical memory. Say, you want to malloc() 1MB of memory on a system that's been up for some time. Physical memory may not have a fitting continuos chunk of memory, but virtual memory of a newly created process will always have one, provided that there is enough free pages available.

In other words without MMU all programs share the same memory space, and if it get fragmented, generally you'd have to reboot. With MMU fragmentation can still be an issue, but it's greatly reduced, since each process has its own memory map. And if memory of the process gets framgmented, you can just restart it. If runtime supports object compaction/relocation, then fragmentation may be not an issue at all.

Re access to memory locations -- mostly any direct access to instruction or data memory in userspace program automatically goes through MMU remapping.

Sorry, I meant to write "voltage regulator" about which parent asked about, not sure how I ended up with "linear regulator".

I believe that without qualification "linear regulator" could be just anything that regulate voltage. Usually you can easily tell from schematics around it if it's some switching IC, an LDO or a module. And if you have layout or 3d render of the board it'd be almost certain.

Otherwise the person may just ask: "where are caps, or is this thing a module or what?"

I've yet to see a voltage regulator IC with built-in caps. DC-DC modules sure, but author argues that this kind of info (module / ic) should be present in schematics. BTW, some linear regulators can't handle ceramic and low-ESR capacitors at output, and may be better with none if that's the choise.

I think he meant that in 3-rd world countries iPhones are luxury items bought by rich people in position of power.

Well racism connotations permeat everything in US, it's overheated/taboo topic there. Not so much in the rest of the world, see two top dictionary definitions from google:

To punish (a person) without legal process or authority, especially by hanging, for a perceived offense or as an act of bigotry.

(Law) (tr) (of a mob) to punish (a person) for some supposed offence by hanging without a trial.

Nothing about racism here. The only thing that doesn't apply to Stallman is that he has not been hanged. That's quite important one. Though words are sometimes used not in their literary meaning (like "I'm killing it" -- well hopefully not).

BTW from what I've gathered this entire thing happened because Stallman was pedantic and has written something along "let's be precise with words, I think what happened was not rape, but statuatory rape because of such and such".

Let's see: - judged by angry mob -- yes, - no ability to defend oneself -- yes, - killed -- no (though seeing polarization and level of anger here it's possible that he'll be eventually physically assulted), - person demolished, life ruined -- yes (Stallman got removed from the org he created, got fired from his work. Another poster here written that his friend got accused, defended in court with hard evidence, life is still ruined).

Comparison with lynching seems fair to me.

All of this got me thinking about creating, you know, accepting tech community where everyone is free to express their own opinions. I'm personally fine with my code being called shit and me being called dumbass for a good measure, just tell me what you really think and we'll sort things out faster instead sugar-coating stuff to not hurt my ego.