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

  • I was about to mod the game for HDR and then found out news of FO4 getting updated.

    Updates break mods. Just how it is. Though, after seeing the work needed for modding Starfield after each exe change, I'm doing shader replacement now. As long as they don't change from DirectX, I should be good.

  • Timestamp in UTC

    But for time of day, use local time and store separate column with the timezone name. Don't use timezone offsets since that doesn't work with DST. You're better off with something like America/New_York because God knows what 2030 will look like.

    And if timezone are abolished, or DST, that's even more reason to store the timezone name.

  • Your dad is right. On desktop, navigation is on the left. On tablet, you shrink it to a rail. On mobile it should be a dismissible nav drawer.

    The top menus, especially the flyover(on mouse hover), are bad for accessibility because they convert a non-committal action (hover) to a context changing one (focus). It's a uniquely web-only invention and thankfully falling out of usage. (Unless you mean menubar/toolbar. Those are fine but extremely rare on Web.)

  • I'm sorry = I am sorrowful (sympathy or empathy)

    I apologize = I am to explain my action (defense)

    Consider:

    • "I'm sorry you feel that way."
    • "I owe you an apology."
    • "What a sorry excuse for a ___ ."

    Meaning, "I apologize" at a funeral is the same as "In my defense..."

  • Yeah, that's a big simplification and I get it. But the async syntax itself syntax "sugar" for Promises. It's not like C# or Java/Android where it will spawn a thread. If you take a JSON of 1000 rows and attach a promise/await to each of them, you won't hit the next event loop until they all run to completion.

    It's a common misconception that asynchronous means "run in background". It doesn't. It means run at end of current call stack.

    Prior to that, the browser had window.setTimeout and its callback for delays and animation and such - but that’s it.

    And you STILL have to call setTimeout in your async executions or else you will stall your UI.

    Again async is NOT background. It's run later. async wraps Promise which wraps queueMicrotask.

    Here is a stack overflow that explains it more in detail.