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/)LI
Posts
0
Comments
117
Joined
2 yr. ago

  • This was a good blog post. I particularly appreciated the statement about the validate and parse function comparison: "Both of these functions check the same thing, but parseNonEmpty gives the caller access to the information it learned, while validateNonEmpty just throws it away."

  • I would love to see professional chess players give this a fair chance. The clock could stop when they declare their move verbally (ensuring that the game doesn't devolve into an endurance test) and start up again for the next player upon the move being completed.

  • There is a market for a game engine that uses algebraic variables and geometry to guarantee purely accurate collision detection. That said, a bit of searching shows that it's going to be much slower then current approximate approaches.

  • I feel almost the exact opposite. I don't feel any progression and I do not enjoy the PvP elements of the game at all. I'm glad that you enjoy it, though.

    Edit: by comparison, I've recently started playing Deep Rock Galactic and feel a great sense of progression without the game-ending effects of PvP. Losing a ship in Eve is a guaranteed time loss.

  • I tried GW2, but I'm just not a fan of the graphics. There are also numerous clipping issues throughout the world. With a game as old as GW2, it worries me that simple vertex issues still exist. I need to see what end-game looks like, though. Maybe it's worth it, idk.

  • I've been playing for the past year and I'm about to quit. It really demands so much time and being on coms. I want an MMO that I can play while I have videos or a movie going on the other monitor.

  • Even if you were using the builder pattern, this maintains the immutable variable in the parent scope while you use the mutable variable's builder pattern methods (basically exactly as my example demonstrates) in the inner scope.

    edit: Oh, I think you mean you would chain the builder pattern calls and assign it to an immutable variable. Sure, that makes sense if you own the struct.

  • I prefer to encapsulate a mutable reference to the instance in a scope.

     rust
        
    let post_form = {
        let mut post_form = PostInsertForm::new(
            // your constructor arguments
        );
        post_form.some_mutating_method(
            // mutation arguments
        );
        post_form
    };
    
    
      

    This way you're left with an immutable instance and you encapsulate all of the logic needed to setup the instance in one place.

  • I wish I could experience that. I wish our sci-fi fairytales of space travel were happening now. Alas, I must simply exist in a life lived better than a king of old, living longer than our ancestors, with food untasted by the billions before us, and all while I fly around in space within Eve Online while watching Star Trek. Life is great, but it's so easy to want it to be just that much better.