Badabinski

That was my interest as well. I never liked the idea of hunting or using guns for self defense. I grew up target shooting, and it was great because it was a sport that a weak asthmatic kid with a flimsy ribcage could take part in. I don’t really do it anymore because I got tired of being around other shooters and I don’t really want to support the industry, but I miss it sometimes.

Yep, and it’s still used in some new ones.

OP is in the US, so no 3 phase power unfortunately ):

I’m hoping you get some good answers. I can’t wear long sleeves in my unheated machine shop (long sleeves + lathe = Very Bad™), and a 20 amp breaker can’t run a lathe and an electric heater simultaneously. I’ve got a diesel heater out there, but it’s just not enough to keep a drafty cinderblock building warm. I get pretty chilly out there, and some kind of battery heated vest would go a long way.

How close does it match this machine translation?

Fuck me until the room stinks

Fair enough. If you haven’t read the books then I’ve heard it’s a fine enough show. I should have written “nothing of value to me was lost.”

Holy shit this sounds rad as fuck. I hope you do eventually write that book.

And nothing of value was lost. As someone who has read that series front to back 4 times, I hated how that show tried to make WoT into fucking grimdark.

Was this done according to proper clean-room design principles? If so, then imo the GPL is still working as intended. The company had to spend a fuckton of money and time getting one engineer to read the source and describe what was done to other engineers, and then ensure that one engineer never ever worked on the project again.

If they didn’t do that then they violated the GPL and someone should report them to the SFLC.

Relevant XKCD.

I bought some SAS leather sneakers this year (I have the opposite problem, my feet are VERY narrow) and I’m hoping they’ll hold up. They seem quite well made, but I’ll have to keep a close eye on them now.

I wrote a program at work that gets deployed to hundreds of thousands of systems and is very hard to fully test or instrument. This program recently had a bug that was hard to track down. Using the command line, I connected to one of these boxes over ssh and ran a series of commands to detect the bug and dump details of what happened. Then, I took all those commands and turned them into a onliner that I could pass in over ssh, so I could get everything I needed for an individual maxhine. I then used xargs to run that command in parallel over every single one of the systems my code was running on and in the end, I was left with a nice directory of files whose name was the IP of an affected system, each filled with useful information. I started by manually running command over ssh, but the composable nature of the shell allowed me to transition that into a script in a matter of minutes.

I provided a more residential example of why I exclusively use the terminal for file management in a different top level comment.

My work and personal computers typically have two applications open—a web browser and a terminal (well, really a shitload of terminals). I don’t have a desktop, I have a terminal. I don’t have a graphical file manager, I have a terminal. I’m not doing this because it’s cool, I do it because it’s efficient as all fuck and makes it trivial to fire off one-liners to automate shit.

Like, I stream a certain video game competitively, and I need to keep recordings if I want to submit runs. I started off recording my gameplay using x264, and the file sizes were too damn big. I tested various av1 options out using ffmpeg on a small sample clip, and when I was done it was simplicity itself to just do this:

# I'm typing this on my phone so I'm not going to write out the ffmpeg args
for file in recordings/*.mp4; do ffmpeg "${some_args[@]}"; done

I didn’t have to learn some stupid GUI batch processing thing. I didn’t have to install any extra tools (since I already had ffmpeg). I just took my command, substituted the input and output files for variable names, and looped that shit.

I feel that the command line is the most efficient interface for a huge number of tasks. Discoverability is awful (although improved with good tab completion and just reading the fucking manual), but the efficiency and composability of a CLI built in the Unix tradition is hard to overstate imo.

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.

Thank you for sharing this fact that has filled me with joy. I am not enough of a science hippy to tell if beer, wine, or bourbon contain more phytoestrogens than soy, but they absolutely do contain it: https://pmc.ncbi.nlm.nih.gov/articles/PMC6761902/

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.

I feel despair every time this project comes up ): I really like the idea of rewriting coreutils in rust, but GNU-compatible coreutils in a permissive license is just asking for trouble…

If you’d like to learn more about Bash itself, this is an amazing resource: https://mywiki.wooledge.org/BashGuide

Probably the ONLY place on the internet that will teach you to write safe shell scripts. Most shit on StackOverflow (and consequently, most shell generated by LLMs) is dangerous garbage.