• 1 Post
  • 67 Comments
Joined 1 year ago
cake
Cake day: July 31st, 2023

help-circle










  • I’d be great if the block would make them unable to downvote you and your posts as well. And it’d be nice if it wouldn’t even let them reply to your posts.

    I’m not entirely sure that’s going to work out the way people think it will.

    Suppose I’m some jackass that gets off on harassing you: if blocks prevented me from interacting with your content, and you blocked me, I would have confirmation that I’ve successfully gotten under your skin. I can then just make another account and continue what I’m doing.

    If blocks don’t notify or provide indication to the blocked party, they would either escalate their behavior (while you are blissfully unaware) and get banned by a moderator, or give up and move on to someone else.

    There’s also considering how that’s going to work with moderators and admins: do they get to bypass the block and continue to comment and interact with you against your wishes? Does it hide your posts from them if they’re blocked? It’s a lot harder to design this type of blocking on a community-centric platform than it is to do for a microblogging platform like Twitter or Tumblr.

    Because muting doesn’t stop the poison the spread, just my personal ability to not see it.

    That’s what mods and admins are supposed to do. It’s not the users’ responsibility to moderate the behavior of others, and it’s a lot less stressful than trying to stop toxicity when you only have words in your moderator toolbox.






  • Recursion makes it cheaper to run in the dev’s mind, but more expensive to run on the computer.

    Maybe for a Haskell programmer, divide-and-conquer algorithms, or walking trees. But for everything else, I’m skeptical of it being easier to understand than a stack data structure and a loop.


  • pivot_root@lemmy.worldtoProgrammer Humor@lemmy.mlStop
    link
    fedilink
    arrow-up
    4
    ·
    edit-2
    2 months ago

    In a single one-off program or something that’s already fast enough to not take more than a few seconds—yeah, the time is spent better elsewhere.

    I did mention for a compiler, specifically, though. They’re CPU bottlenecked with a huge number of people or CI build agents waiting for it to run, which makes it a good candidate for squeezing extra performance out in places where it doesn’t impact maintainability. 0.02% here, 0.15% there, etc etc, and even a 1% total improvement is still a couple extra seconds of not sitting around and waiting per Jenkins build.

    Also keep in mind that adding features or making large changes to a compiler is likely bottlenecked by bureaucracy and committee, so there’s not much else to do.


  • Not necessarily. It depends on what you’re optimizing, the impact of the optimizations, the code complexity tradeoffs, and what your goal is.

    Optimizing many tiny pieces of a compiler by 0.02% each? It adds up.

    Optimizing a function called in an O(n2) algorithm by 0.02%? That will be a lot more beneficial than optimizing a function called only once.

    Optimizing some high-level function by dropping into hand-written assembly? No. Just no.