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

  • It'd be great if they truly believed this, but that's just the image they like to project, the truth is that this has them deathly afraid.

    You've got mainstream media covering it, folks like digital foundry openly talking about how Windows is the worst part of Windows handhelds. They can't let this stand, so they're actively working against it.

    Just like the faster zombies blog post in 2012 scared them into boosting d3d development and eventually led to the release of d3d12, this will make them actually invest in gaming for a change.

    All the chatter about xbox branded handhelds is an easy tell, but like the blog post we might not discover the true extent until years later.

  • It ends up being complex, but it doesn't start that way.

    These games are very long and the mechanics are slowly added in tutorialised fights spread out over the story.

    In practice this means the battles are dead simple for the first ten hours of gameplay, you'll be 40 hours into the game and still get tutorials.

  • English has the peculiarity of having two variants of the same word: "gender" and "genre" with slightly different meanings.

    You could lean on it and go with genre. But just changing the word is unlikely to help much, the concept itself is deeply associated with genitalia in English culture, you'd still need to explain it.

  • Regardless of what the website says, waydroid isn't an emulator by any meaningful definition.

    It's a container that runs on top of your regular linux kernel (with some very cool desktop integration features), java/kotlin applications run as natively as they'd run on your phone.

  • I felt the same way about webp when it came out.

    In practice it doesn't really matter:

    • if you're encoding the file you know how you're doing it.
    • if you're receiving the file, you get the pixels you get no matter how it was encoded.
    • if you're sending the image through some third party service, they're going to reencode and mangle it anyway so there's no point in worrying.

    Also, it turned out that even if it's quite good, lossless webp is rarely seen in the wild because svg is more convenient.