Badabinski

Man, that’s cool! Concrete is a heck of a lot cheaper than epoxy granite resin and is perfectly suitable for a low-precision tool like this lathe.

I do hope that he finds a way to shield those bearings. You really don’t want metal chips or sawdust making its way in there. Any damage they sustain will cause runout, which will lead to increased chatter and parts that are out of spec. Plus, a matching pair of tapered roller bearings can be quite expensive!

EDIT: to be clear, I mean no disrespect when I say low-precision. Not every lathe needs to have slides and handwheels. I have a little Sherline lathe that I’ve used like this in the past (using gravers, not tools in a tool holder). It’s great to quickly turn something or to put nice decorative details on a part. Precision is possible with a lathe like this, but it requires fairly strenuous effort.

I just have the 0.6mm nozzles mine came with. I recall hearing something like that, but I’ve felt that the phat 0.6 lads were good enough for the stuff I’m printing. If that’s a limitation, then I hope Prusa can fix it. Seems like it shouldn’t be a big deal to make that configurable.

I own a Prusa XL and I love it. it’s the most reliable printer I’ve ever owned by a long shot. The only thing I’ve been unhappy with is the somewhat lackluster support for Octoprint, but I’ve heard that others have been able to fully use the printer with the right configuration.

Yeah, the time drift between the earth and moon is small, but it’ll noticable for latency-sensitive software.

God, I’d hate to be the dev that has to deal with relativistic time zone conversions. What a fucking nightmare that’d be…

I liked how each of the sections ended with a different game that she’s gotten running so far. It makes the article feel like a progressively bigger flex, which, of course, it is. Awesome to see this work progressing!

Fuckers. I don’t know why you’d want to hack the IA, but they’re dicks for doing so. I’m gonna throw some of my spondulix to the IA, and I’d encourage others to do so.

As others have said, email is a great way to get the point across without getting into nerd shit. I just say something like this: “You know how you can have an email account with Microsoft and can send messages to an email account at Google? Lemmy is that, but instead of sending and receiving emails, you’re looking at, voting on, and leaving comments on posts like you would on Reddit.”

I have had a 100% success rate with this analogy when the person I’m talking to knows what Reddit is. If they don’t know, then I don’t really bother explaining it since it’s likely outside of their interests. I’m not out proselytizing for the Fediverse, but it comes up on occasion (especially when I share a links to shitposts).

The arch wiki has a udev rule that can automatically do something if the battery crosses a certain threshold: https://wiki.archlinux.org/title/Laptop#Hibernate_on_low_battery_level

No polling which is great. I always try to do stuff on an event driven basis where possible for efficiency reasons. Gotta test this out though, since your battery might not send events for every percent change.

It very definitely was 😅 The way that company used the satellite network was cool, don’t get me wrong. They would use it to push content out to all their stores with multicast which was really efficient with bandwidth. I loved it for that, but I hated interacting with it over unicast in any way, shape, or form. Horses for courses, as they say.

The screenshots look really nice. I’ve personally always struggled with designing nice TUIs, so I really appreciate the way this looks.

I’d recommend trying out shellcheck and potentially building it into your repo as a CI check. I’ve written a ton of Bash over the years, and I’ve found shellcheck to be absolutely essential for any script over ~100 lines. It’s not perfect, but it does do a great job of helping you avoid many of the foot guns present in Bash. I also dearly love this site. It’s a fantastic reference, and I look at it almost every day.

I may take some time later today and provide a bit of specific feedback.

My pain tolerance for shitty input methods has been permanently warped after experiencing psychic damage from using Teamviewer to connect to a system over a very flaky HughesNet satellite link. I was working for a vendor that supplied a hardware networking box to a stupid retail company that sells food and shit. I just wanted to ssh to our boxen on a specific network so I could troubleshoot something, but the only way I could get to it was via putty installed on an ancient Windows XP desktop on the same network as our box that could only be accessed with Teamviewer. My favorite part of that was that the locale or something was fucked up, so my qwerty keyboard inputs were, like, fucking transformed into azerty somehow?? The Windows desktop was locked down and monitored to a tremendous degree, so I couldn’t change anything. The resolution was terrible, the latency was over a second, and half of my keyboard inputs turned into gibberish on the other side.

Oh, and I was onsite at that same company’s HQ doing a sales engineering call while I was trying to figure out what was wrong. I spent 5 days sitting in spare offices with shitty chairs, away from my family, living that fucking nightmare before I finally figured out what was wrong. God damn, what a fucking mess that was. For anyone reading this, NEVER WORK FOR GROCERY/DRUG STORE IT. They are worse than fucking banks in some ways. Fuck.

EDIT: also, I asked ‘why Teamviewer’ and the answer was always shrugs. This was before the big TeamViewer security incidents, so maybe they thought it was more secure? Like, at least they didn’t expose RDP on the internet…

Having been in this situation (the only binary I could use was bash, although cd was a bash builtin for me), echo * is your friend. Even better is something like this:

get_path_type() {
    local item
    item="$1"
    [[ -z "$item" ]] && { echo 'wrong arg count passed to get_path_type'; return 1; }
    if [[ -d "$item" ]]; then
        echo 'dir'
    elif [[ -f "$item" ]]; then
        echo 'file'
    elif [[ -h "$item" ]]; then
        echo 'link'  # not accurate, but symlink is too long
    else
        echo '????'
    fi
}

print_path_listing() {
    local path path_type
    path="$1"
    [[ -z "$path" ]] && { echo 'wrong arg count passed to print_path_listing'; return 1; }
    path_type="$(get_path_type "$path")"
    printf '%s\t%s\n' "$path_type" "$path"
}

ls() {
    local path paths item symlink_regex
    paths=("$@")
    if ((${#paths[@]} == 0)); then
        paths=("$(pwd)")
    fi
    shopt -s dotglob
    for path in "${paths[@]}"; do
        if [[ -d "$path" ]]; then
            printf '%s\n' "$path"
            for item in "$path"/*; do
                print_path_listing "$item"
            done
        elif [[ -e "$path" ]]; then
            print_path_listing "$path"
        printf '\n'
        fi
    done
}

This is recreated from memory and will likely have several nasty bugs. I also wrote it and quickly tested it entirely on my phone which was a bit painful. It should be pure bash, so it’ll work in this type of situation.

EDIT: I’m bored and sleep deprived and wanted to do something, hence this nonsense. I’ve taken the joke entirely too seriously.

Nolla. They make great games with interesting vibes!

oh fuck I did misread it. Man, now I sound like a big ol’ asshole. Sorry, OP :/ I had a bad week thanks to some ChatGPT code and just kinda jumped out when I saw the word “ChatGPT” next to Bash.

Ugh, I hate ChatGPT. If this is Bash (which it is, because it’s literally looking for files in a directory called ~/.bashrc.d), then it should god damned well be using syntax and language features that we’ve had for at least twenty fucking years. Specifically, if you’re writing for Bash (and not POSIX shell), you better be using [[ ]] rather than [ ]. This wiki is my holy book I use to keep the demons away when writing Bash, and it does a simply fantastic job of explaining why you should use God damned double square brackets.

ChatGPT writes shitty, horrible, buggy ass Bash. This is relatively decent for ChatGPT (it even makes sure the files are real files and not symlinks), but I’ve had to fix enough terrible fucking shitty AI Bash to have no tolerance for even the smallest misstep from it.

Sincerely, A senior developer who is known as the Bash wizard at work.

EDIT: Sorry, OP. ChatGPT did not, in fact, write this code, and I am going to leave my comment here as a testament to what a big smelly dick I was here.

the ability to write to busy executable files

Thank god, this has been such a pain in the ass for SO LONG.

Don’t forget fully automated!

Hopefully we’ll be able to find a working one soon :( our emissions here are exclusively OBD2 based for anything 1996 or newer. I’ll probably do what some other folks have recommended and try to “remanufacture” one myself.

EDIT: no idea why my client decided to post my comment twice.

deleted by creator

For me, it’s Arch for desktop usage. When I first started using Arch it would not have been Arch, but now it’s Arch. The package manager has great ergonomics (not great discoverability, but great ergonomics), it’s always up to date, I can get a system from USB to sway in ~20 minutes (probably be faster if I used the installer), it’s fast because it doesn’t enable many things by default, and it’s honestly been the most reliable distro I’ve ever used. I used to use OpenSUSE ~10 years ago, and that broke more in one year than Arch has in ten.

I personally feel like Arch’s unreliable nature has been overstated. Arch will give you the rope to hang yourself if you ask for it, but if you just read the emails (or use a helper that displays breaking changes when updating like paru) and merge your pacnews then you’ll likely have a rock solid system.

Again, this is all just my opinion. It’s easy for me to overlook or forget all of the pain and suffering I likely went through when learning how to Arch. I won’t recommend it to you, but I’ll happily say how much I’ve come to enjoy using it.