• 22 Posts
  • 30 Comments
Joined 2 years ago
cake
Cake day: August 2nd, 2023

help-circle































  • Here’s a recent HN thread about the objects: https://news.ycombinator.com/item?id=35937540

    Metalworker status symbol seems compelling, as it explains several facts about them, and the knitting angle could be a chicken vs egg situation. Either knitters found an existing and relatively common object to be useful for their needs, or knitting is older than we think and the need for these tools drove metalworkers to decide that a hard-to-make tool was a good status symbol. Or maybe it’s both/and, with both needs influencing each other. I can easily imagine some metalworking culture deciding that this hard-to-make tool is a good status symbol, and they eventually turn it into something that’s not actually useful for the original purpose, but works great to show off.









  • m_f@midwest.socialtoProgrammer Humor@programming.devGolang be like
    link
    fedilink
    arrow-up
    18
    arrow-down
    2
    ·
    2 years ago

    You probably wouldn’t be committing this, unless you’re backing up a heavily WIP branch. The issue is that if you’re developing locally and need to make a temporary change, you might comment something out, which then requires commenting another now-unused variable, which then requires commenting out yet another variable, and so on. Go isn’t helping you here, it’s wasting your time for no good reason. Just emit a warning and allow CI to be configured to reject warnings.