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/)JU
Posts
15
Comments
733
Joined
11 mo. ago

  • You don't even have to listen to a podcast to find out how misguided this comment is. Click the link, it's all transcribed. It's not a question, it's a guide.

    If you're not interested in the content, scroll past instead of being rude to people.

  • Are you required to use the Microsoft Suite or do they only care about the resulting file type? I would just use Libre if the latter, although I'd suggest spending a day or two getting used to the slightly altered workflow before introducing it to your work life.

    If the former, keep it in the browser like others have mentioned. Web apps are kinda the direction they're moving anyway, so I wouldn't be surprised if we're all getting used to them in a few years anyway

  • I don't the point of advertising. If you make a good product, people will naturally buy it.

    You're probably not wrong if I'm completely honest, but this feels intrinsically wrong to my capitalist-addled brain. Something to work on I guess

  • You should check out the next 5 verses of that. James 5:1-6. It's gotta be one of my favorite bits from the bible. I would put it here, but I kind of wonder if enough people start googling it if the powers that be will notice

  • My point was "are state machines really that complicated? Isn't it just something like this pseudo code and a return value from your functions?"

    Basically I feel like this is a 2 step process but you seem like you either know more than I do or have a different philosophy about how this would be implemented, so I want to understand what I'm missing

  • This is a great explanation except for one detail. Stability refers to release cycles in the Linux world, so your description of stability is a little redundant. The word you're looking for is reliability, but all 3 of the giants provide that.

    The release cycle and the package managers are the two biggest factors that most people decide their distro based off. There are some more considerations as you get deeper into the Linux world, like your init system and whatnot, but those two are the big drivers IME.

  • Complexity being added at updating also feels wrong to me. Let me pseudo code some rust (just the language I know best off the top of my head right now) at you, cause it feels like maybe I'm just not understanding something that's making this seem easier than it is.

     Rust
        
    Enum Game_State
        Paused
        Paused_Saved
        Running
        Loading
        Exit
     
    ///Technically you could make Menu() part of the enum but I'd probably leave it elsewhere
    
    Match Game_State
        Paused => Menu()
        Paused_Saved => Menu()
        Running => Main_Loop()
        Exit => Exit()
    
    
      

    And then your other functions always return a game_state. You're right that adding that return would be a huge undertaking if it's not handled in the initial building of the game, but it's a QoL for the user that's easily maintainable and is therefore worth doing IMO. But these two things, defining the possible game states and then always routing decisions through that game state, makes this kind of feature relatively doable

  • Non judicial punishments and courts martials make up the american military legal system.

    NJPs are basically your commanding officer saying "you did this wrong, you're grounded. Half pay and stay in your room for a month"

    Courts martials are an actual legal proceeding with a military judge who says "you did this wrong, straight to jail. Do not pass go, do not collect $200"

    All this to say, yes. In fact, there are jobs in the military that can be legally punished with execution if they aren't performed diligently even during peace times.

  • I think we write our code in different enough ways that we're not seeing eye to eye.

    Tracking the state of the game being paused, when the menu is open and when the game is saved can all be a single match statement on a current "game state" variable which just holds "running/paused/paused and saved/exit" and when it becomes exit, it checks the save time. Only 2 lines of code and adding an enumerated state to the variable to add this functionality. Since the variable is enumerated, it's really difficult to mess it up when refactoring because if you can't pass the wrong code or else your game doesn't save or close

  • I feel like I've seen a "Time since last save:" line on enough games to find it hard to believe that "paused and saved" is difficult to check for lol

    These are variables that already exist in most games, it just needs one more line of code to check them

  • Depends how well you know the person. I know my work wife is coming even when people are yelling and machines are running around me, but if Ben doesn't say something when he walks up behind me I'll have no idea he's there

  • No. As a matter of fact, this is a neat party trick I used to use.

    Start with literally any number, and count the letters to match it. You will always end up at four because it's the only English word and Arabic numeral represented with equivalent letters.