• 0 Posts
  • 9 Comments
Joined 7 months ago
cake
Cake day: September 15th, 2024

help-circle

  • As I understand it, switch 1 digital games are console-bound, but you can migrate your whole console to a new device (such as if your switch breaks.). This was terrible and unfriendly, and why almost all of my family’s switch games are physical.

    I doubt “share once and let everyone play but the owner” was an intentional promise from Nintendo, but I’d have no trouble believing a tale about their DRM checks leaving open a hole like that.



  • Steam sells non-transferable lifetime licenses to each game you “buy”, that let you play it on one PC at a time but never transfer it to anyone else, even as part of an inheritance after your death.

    If you have a family there is a “sharing” plan which allows you to let family members also play some of the games in your library, but not at the same time.

    Nintendo is imposing a bit more ceremony if you want to share digital games each time you share them, but the essential “one device at a time” nature is the same that steam imposes.


  • Nintendo made a huge deal about virtual game cards, saving us from exactly what you’re afraid of.

    Not as good as what Sony and Microsoft do, where we can essentially install our whole library on every console we have, but it’s about as good as what Steam does.

    Plus they’re bringing back a “game share” like feature, so some multiplayer games should be playable in a local family with only one purchase.





  • Because neither Kotlin nor JavaScript load images.

    Kotlin is a Java runtime language, whose most common use is being compiled to bytecode to run full desktop or server applications.

    JavaScript is a web browser language, whose most common use is being sent alongside HTML to augment the behavior of a web browser.

    Since Kotlin tends to operate outside of a browser sandbox, it makes sense to expose JRE features to allow memory efficient image handling.

    In contrast, JavaScript within a browser sandbox only gets images loaded by the web browser, which were already sent over the Internet and loaded in their full size.

    ( There are ways to run JavaScript outside a browser and Kotlin within, but that’s a bigger topic.)