HN user

icedchai

10,090 karma
Posts3
Comments6,651
View on HN

I have a AMD Strix Halo box I use for similar dabbling. It definitely wasn't an "out of the box" experience, fiddling around with kernel versions and ROCm installs. These days I mostly wind up using the Vulkan build of llama.cpp for inference.

AI documentation is also often incredibly verbose. It makes it difficult to see the forest through the trees. I am often repulsed by the README.md in many "AI generated" projects.

Vendor terminology is often different (tagged VLANs vs trunking, etc.) but, in general, it is close enough that an experienced person can figure it out with a bit of googling. I've built networks with Cisco, Mikrotik, Aruba/HP, custom Linux routers, and others. Mikrotik VLANs are a bit weird, for sure.

In today's world, is generally easy to get things to communicate. It's not 30 years ago and nobody is running DECnet, Appletalk, or IPX.

I've worked with developers that don't even understand that the "form" tag exists and browser can send a request without any javascript. At some point in the early 2010's, perhaps even before, fundamental understanding disappeared. This makes it difficult to introduce alternative technologies like HTMX into a larger project.

Yep. I’ve worked on some federal contracts and all the waste is in private contractors, not the government itself. There are structural issues with subcontractors many layers deep, each middleman taking a cut for doing little to nothing. It’s sick.

8 months ago you could get one of these for ~$2K. Well, not this exact item, but systems like the Framework Desktop with the same CPU and memory configuration.

It was a good deal for $2K. For $4K? I'm not so sure. Of course, most of the cost is RAM, so what can we do?

What you describe is a user and resolver configuration problem. There are 100's of TLDs and there's always a chance they will conflict with subdomains, either now or in the future as new TLDs are created. I've been using both "int" and "dev" as subdomains since at least 2000 and never had an issue.

Yep, it definitely wasn't an "out-of-box" experience. This was on Ubuntu 25.10. Maybe other distros are better?

Also, when you do Python work, you have to remember to install dependencies like pytorch from an alternate repo, otherwise you wind up with the CUDA versions that only use the CPU and not the GPU through ROCm.

The "ROCm" situation with Strix Halo was pretty bad for a while. I think it finally stabilized late last year. You needed the right combo of ROCm, Linux kernel, and kernel firmware for it to work reliably.

Whenever I rebuild llama.cpp, I wind up using the Vulkan build anyway.

In the alternate reality where this happened, wouldn't the price of DDR4 still be sky high? We'll ignore any costs for CPU, chip set, and motherboard redesign. You're just pushing the demand somewhere else.

Yep, the only reason I bought mine (in late 2025, before hardware prices went totally crazy) was because it was half the price of a Spark. I spent a while fiddling around with the right Linux kernel, kernel firmware, ROCm installs, etc.