Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)E
Posts
9
Comments
175
Joined
2 yr. ago

  • hey, a/s/f?

    Also seems ripe for jokes about the missing d.

    Though I guess the reasoning for why they're changing it up is actually decent:

    changing its corporate logo and overhaul its branding after being criticized by American Indian activists.

    It's the sort of thing that I think a lot of europeans will go "huh, what does a feather … ohhhh, riiiiiiiight …". Like, my associations to the name are mostly the LAMP stack and a model of children's bike that my parents have talked about. But we're collectively also always rolling our eyes at people, especially foreigners, using stuff related to our heritage as marketing. Can't imagine what that'd be like for the native americans and their history.

  • Well, bash should show up quickly enough. But yeah.

    I'm also no longer much of a bash guy. Back when I was my scripts were a lot simpler, and broke in weird ways a lot more. And every time I picked up a new defensive habit, my bash became a little bit uglier, and I thought to myself "maybe I should just do this in Python".

    But this script would be a lot longer in Python.

  • IME I'll rather find some openapi docs for Google than their actual product docs. As in, I'll start out trying to read their kubernetes docs, then shortly after it's "fuck it, I'm going to docs.rs/k8s-openapi".

    My actual worst case are Elastic's docs, though. Somehow they have plenty of stuff in there, just never the stuff I'm trying to figure out.

  • For those who want to give it a go:

     bash
        
    #!/bin/bash
    set -euo pipefail
    
    while read -rd ":" path
    do
      for bin in "$path"/*
      do
        # don't error out if there's no manpage
        set +e
        man "$(basename "$bin")"
        set -e
      done
    done < <(printf '%s%s' "$PATH" ":")
    
      

    when you get sick of it, hit ^Z (ctrl-z) and go kill %1. Then you get to start all over from the start next time!

    Bonus points for starting a tracker so you can count how long it takes to go from "eugh, what's with that overwrought and excessively defensive bash script" to "fuck, now I'm doing it too"

  • Humans also frequently need to try a wrong approach first to get the idea of a better approach, no matter if we're rested or not. Which is why it's important to be able to throw away prototypes rather than push an "it seemed like a good idea at the time" to prod.

    But having a good sleep, walk in a park, shower, etc lets us think better than if we're just banging our heads in the same corner all day long. Breaks are important. General health, too.

  • Removed

    SHUT THE FUCK UP!

    Jump
  • But what did you learn? What are we supposed to learn? Did you get any context, like how he actually went to anger management therapy later?

    Or is this just guffawing and gawping at an old angry email from a tech celebrity?

  • Removed

    SHUT THE FUCK UP!

    Jump
  • This mail is 13 years old, and doesn't seem relevant for anything? This post seems like a lazy attempt at shit-stirring.

  • The fourth … appendage on the left hand is being used like a thumb, and doesn't have any indication of knuckle even though it'd be the most bent finger if it was one. I'd say we can see four fingers on the right hand, while the left is in an indeterminate slop state where it's only partially a comic/Disney three-finger hand, with one extra slop appendage that's not clearly either thumb or finger.

  • Part of the answer here is also integrated design. To be able to be repaired a thing has to be designed for that, and to have identifiable parts that can be adjusted or replaced in isolation, and non-destructive disassembly.

    If you have to destroy one part to adjust another, it's not really repairable. If several functions/components are all one thing then you can't really replace just the one.

    To use a bike as an example, you can exchange wires, brake pads, seats and most other things in isolation, especially the things that are expected to wear out and need replacement. But you're not going to replace part of your bar tape or frame, because they're essentially one whole thing.

    (Ok, you could probably weld a steel frame if you really wanted to, but I think the intent is readable.)

  • If usps doesn’t want to deliver to rural addresses, fine, but set up some alternatives. Create a secured remote mailbox, or offer P.O. Boxes for free.

    The fundamental problem here is that the US population doesn't really want to pay for stuff where they don't directly benefit. In "me first" politics, rural populations are screwed.

  • Same reason as the vampire has one hand with four fingers and fingernails, and one hand with three fingers and no nail: LLM slop

  • Kinda. At the last strand I expect them to switch to length.

    But yeah, at some point should be good enough

  • We could probably stand to have some organisation standards in repo roots, but I tend to agree that dotfiles aren't the way to go there. The project root is similar to ~/.config and the like: When you're there you should not be subjected to further hidden levels. Those config files are a significant part of the project.

    State files however, like all the stuff in .git, lockfiles and the like are generally¹ fine to hide away. Those are side effects of running other tools, not ordinary editable configuration. Same goes for cache—and both cache and runtime files should likely go in the ordinary XDG dirs rather than be something every project has to set up a gitignore for.

    If anything I'm more frustrated with the C projects that just plop every source file in the root directory.

    ¹ Just don't make it too easy to sneak unexpected crap in there. We don't need to make the next Jia Tan's job easier.

  • There's wasm if you need to target browsers.

  • Similar in Norwegian: Ugress. Un-grass.

    I've heard one definition of it that I like: The grass that your (grazing) animals won't eat.

  • We’ve also recently introduced Coding Challenges to our site! These new challenges represent a new, fun way for developers to level up by tackling captivating puzzles and earning recognition for your skills and creativity. It’s a rewarding way to practice and expand your knowledge with the Stack Overflow community in a space that celebrates diverse and unique approaches.

    aka

    pls provide training material for the LLMs for free :pray:

    lol. lmao, even

  • That's how it starts. Just let it develop for a century or something and you'll probably be decent at it

  • Yeh. Ubuntu also discussed it back in 2019, and wound up keeping some of it so Steam would keep working.

    I expect the willingness to bend over backwards for one proprietary and very profitable app doesn't last forever, and given how involved gaming often is with pushing technology, it's frankly weird that Steam is still shackled to 32bit like that.

  • Yeah, I think the fact that the next LTS will be 26.04 is the driver here, I just get the impression that things might get a little rocky and that they might've been better off had the next LTS been further into the future.

    But it'll be a real smoke test release, at least. Hopefully they have enough resources to fix the issues that are uncovered, and don't wind up reverting for the LTS, or with a crummy LTS.