Readit NewsSo my 4090 (24 GB) is probably going to get turned into a 48/96 GB VRAM frankenstein in a Chinese chop shop. I haven't watched the full 3.5 hour documentary you linked but from the first few minutes, it seems quite interesting. And covers this exact thing.
Edit: Again, I checked the address, it was a house, not a freight forwarder warehouse. And if it was actually going to AU, the forwarder would be on the west coast in CA/WA, not east coast (had another order go to Thailand with a forwarder in SF. And Miami is the big hub for South America). For legit freight forwarding they also wouldn't have different names on the account & shipping address. As the parent comment's YT video describes, these are often just normal Chinese-Americans or international students who do this to make a bit of extra money.
> So they're shutting down their consumer memory lines, and devoting all production to AI.
Okay this was the missing piece for me. I was wondering why AI demand, which should be mostly HBM, would have such an impact on DDR prices, which I’m quite sure are produced on separate lines. I’d appreciate a citation so I could read more.
NVIDIA started allocating most of the wafer capacity for 50k GPU chips. They are a business, its a logical choice.
they still do it because you can't play all the multiplayer games with kernel level anticheats
But I totally agree, I still install windows for gaming on my machine, but it looks like that for my purpose of gaming I can stay with Linux (I play mainly older games or indie games).
This should have been a VM with a basic server and socat’ing the vsocket. I don’t know why so much space was dedicated to unrelated topics. Also zero qualifications or benchmarks for “fast” compared to tcp/virtio.
Author says “no ssh keys” when ssh is an orthogonal concept. sshd can listen on a vsock interface, it’s not specific to tcp/ip.
From the “Under the hood” section, which should be the part actually about vsock:
> I haven’t delved into the low-level system API for vsocks, as frameworks typically abstract this away.
This is just what happens when you use bazel to quickly set up your project.
The first release of git was in 2005, around a decade after Windows 95.
> Instead of
>
> source .venv/bin/activate
> python myscript.py
>
> you can just do
>
> > uv run myscript
>
Side rant: yes I get triggered whenever someone tells me "you can just" do this thing that is actually longer and worse than the original.
This all seems sensible for languages like C or Zig that neatly cross compile to WASM. But I was very confused how this could ever work with a duck-typed interpreted language like Python, so I did some digging.
Apparently "run your Python as WASM" part is implemented by componentize-py which cross compiles CPython to WASM as libpython3.14.so [2].
I'm not sure whether I should be impressed or horrified...
[1] https://component-model.bytecodealliance.org/
[2] https://github.com/bytecodealliance/componentize-py/blob/79e...