this post was submitted on 15 Oct 2024
215 points (96.5% liked)

Games

16761 readers
1051 users here now

Video game news oriented community. No NanoUFO is not a bot :)

Posts.

  1. News oriented content (general reviews, previews or retrospectives allowed).
  2. Broad discussion posts (preferably not only about a specific game).
  3. No humor/memes etc..
  4. No affiliate links
  5. No advertising.
  6. No clickbait, editorialized, sensational titles. State the game in question in the title. No all caps.
  7. No self promotion.
  8. No duplicate posts, newer post will be deleted unless there is more discussion in one of the posts.
  9. No politics.

Comments.

  1. No personal attacks.
  2. Obey instance rules.
  3. No low effort comments(one or two words, emoji etc..)
  4. Please use spoiler tags for spoilers.

My goal is just to have a community where people can go and see what new game news is out for the day and comment on it.

Other communities:

Beehaw.org gaming

Lemmy.ml gaming

lemmy.ca pcgaming

founded 1 year ago
MODERATORS
nanoUFO@sh.itjust.works
215
Nintendo, famed for hating emulation, likely using Windows PCs to emulate SNES games at its museum (www.techspot.com)
submitted 1 month ago by nanoUFO@sh.itjust.works to c/games@sh.itjust.works
15 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] kibiz0r@midwest.social 1 points 1 month ago

The Switch is ARM and uses several components from FreeBSD and Android. It would not be surprising to learn that they have the ability to compile system components like Virtual Console for an ARM Linux with stubs for Switch-specific stuff.

The SNES Classic is also ARM, and has much less going on than the full Switch OS (Horizon). That could be the core of what they use for the museum displays, considering there’s an ARM version of Windows too.

Either way, devs gonna dev. If you can’t get feedback at your workstation and always have to deploy to your target platform to test anything, you’re gonna move too slow to catch and fix bugs or build flexible enough systems to prevent them.

So much of dev testing is about trade-offs between rapid iteration and thorough fidelity. You need access to both.

From my own experience, I’ve done stuff like:

  • built mobile apps that can also be deployed as desktop apps or web apps for the sake of dev testing
  • built testing tools for car systems that fake out sensor input
  • built HTTP wrappers for cloud-deployed services to allow them to be run locally
  • faked out camera feeds for AR apps

It can get janky, cuz not everything works the same way, but most of what you work on is not platform-specific anyway and a good architecture will minimize the portion of code that only works on the target platform.