Badabinski

Yeah, 88/2 is weird as shit. Perhaps the GPUs are especially large? I know NVIDIA has that thing where you can slice up a GPU into smaller units (I can’t remember what it’s called, it’s some fuckass TLA), so maybe they’re counting on people doing that.

This is the most important piece of information. You should edit the post and/or title to make this more clear.

I hadn’t even thought of that! I did some oxyacetylene welding many moons ago and I remember the heat being absolutely intolerable at times.

I do machining as a hobby now and I’d really like to filter out cutting oil smoke. My biggest fear using a PAPR is my shop is the hose—I’d need to find a way to keep it REALLY close to my body. I don’t want to get pulled into my lathe face-first.

I very much want a PAPR as well. I seem to recall that there were some units that came out of COVID that are somewhat cheaper, at least.

Yo, I think your shit got hacked.

AFAIK, LFP thermal runaway can’t start fires. NMC or other lithium chemistries can and they scare me, but LFPs are pretty damn safe. That being said, I’m still stoked for sodium chemistries to be developed. If the round trip efficiency issues can be solved, then I think it’ll be a great solution for residential power storage.

I made the mistake of buying a Samsung washer/dryer set in 2017. The washer actually still works and the seal has held up well, but the dryer drum jumped its tracks within the first year, and both have been plagued with gremlins.

Fuck Samsung appliances and honestly most things Samsung sells.

I’m not using it because it would be extremely inconvenient for me, but I think that the English language deserves to have the thorn returned to it.

Where would be manually modifying modules.dep and map files on this, I wonder?

it was a form from Google soliciting feedback on the thing.

Lovely, thank you for this. I’ve left my feedback, and I hope many, many other people do as well.

It also lacks any form of dependency management AFAICT. I don’t think there’s any way to say you depend on another service. I’m guessing you can probably order things lexically? But that’s, uh, shitty and bad.

I wrote and maintained a lot of sysvinit scripts and I fucking hated them. I wrote Upstart scripts and I fucking hated them. I wrote OpenRC scripts and I fucking hated them. Any init system that relies on one of the worst languages in common use nowadays can fuck right off. Systemd units are well documented, consistent, and reliable.

From my 30 seconds of looking, I actually like nitro a bit more than OpenRC or Upstart. It does seem like it’d struggle with daemons the way sysvinit scripts used to. Like, you have to write a process supervisor to track when your daemonized process dies so that it can then die and tell nitro (which is, ofc, a process supervisor), and it looks like the logging might be trickier in that case too. I fucking hate services that background themselves, but they do exist and systemd does a great job at handling those. It also doesn’t do any form of dependency management AFAICT, which is a more serious flaw.

Nitro seems like a good option for some use cases (although I cannot conceive why you’d want to run a service manager in a container when docker and k8s have robust service management built into them), but it’s never touching the disk on any of the tens of thousands of boxes I help administrate. systemd is just too good.

Just journalctl | grep and you’re good to go. The binary log files contain a lot of metadata per message that makes it easy to do more advanced filtering without breaking existing log file parsers.

I’ll agree that list comprehensions can be a bit annoying to write because your IDE can’t help you until the basic loop is done, but you solve that by just doing [thing for thing in things] and then add whatever conditions and attr access/function calls you need.

The one where every LLM-generated shell script I read is another deep splinter in my fingernail quick that I have to rip out and destroy because it’s a godfucked mess of bad practices that we can never ever ever ever EVER train out of an LLM at this point.

I think a new GPL needs to be created to account for this. Like, “any generative system using this as an input which can ever replicate this code base (even in part), must be bound to this license.” People could then run overfitting analysis to see if they ever get their copyleft code out of the model. If they do, then they have grounds to sue. I’m fine with an LLM being trained on my code, but I want the four freedoms to be preserved if it is.

Open source isn’t good enough, I want my software to use a strong copyleft license with no ability to relicense via a CLA (CLAs that don’t grant the ability to relicense software are rare, but acceptable). AGPL for servers, GPL for local software, LGPL for libraries when possible, and Apache, MIT, or BSD ONLY when LGPL doesn’t make sense.

There’s still a place for producing hydrogen via electrolysis (chemical feedstock), but anyone who wants to burn hydrogen is either selling you a rocket (good) or an excuse to keep sucking up that crude. The answer to our energy problems is still just solar, wind, batteries, and other renewables.

I’m positive it has the same issues as any other Windows VM setup. If you’ve got two GPUs, you can probably pass one of them through to the VM and get good graphical performance.

I wish the virtio-gpu stuff hadn’t died on Windows…

EDIT: It might not be dead? That’s cool if so.