Porting Zelda Classic to the web

No, what I am suggesting is to add the basic UI and audio stuff and leave it at that for a large class of applications.

Then the rest of the features should not be one monolothic bundle. Because what that does it make it so that you have to implement every API in order to be compatible with the platform. Which is impossible unless you are a large corporation.

The platform should be carefully explicitly designed to allow subsets of functionality to be implemented and distributed.

Again, starting with the very most basic UI stuff as one common chunk. Without all of the other features and devices.

The point of this is to make it feasible to have many implementations of different types of browsers or subsets of functionality. This prevents us from being locked into a single dominant vendor or two.

The information browsing can actually be the first subset of functionality. Very simple small vector images and a relatively small amount of RST or markdown. Many different groups can make information browsers.

Then you have the next level up / type of functionality which is basically web assembly SDL. This would be used separately but in conjunction with the information browsers.

You could standardize on another set of functionality with shaders and networking support. Or, if you do it right, it may be possible to create a common web assembly interface for each feature, and package up the additional features into something like device drivers which could be shared across "extended" browser implementations. This would allow for diversity of extended media browser implementations as well as alternative "drivers" to be available.

Wow lots of people here who played Graal. I spent 10 years of my life on that game and I can credit it with giving me my start in development. Learning to script for the game became my first step towards programming in general.

In fact, developing new content for the game became the fun itself.

Codein here btw (ignore the icky nickname - is what it is).

Great writeup!

Trying it out, it does not load in Firefox 81 (potentially due to some restrictive security setting here?) but runs great in Chromium after an update.

Nintendo have had a conflicted stance about community projects over the years. From threatening UltraHLE (early Nintendo 64 emulator) developers back in the late 90s to largely ignoring the Wii exploits and homebrew scene in the mid-to-late 2000s to attempting to hire private investigators to identify and implicate 3DS homebrew developers in 'illegal' activities.

A similar case is when the PS3 Slim was released without OtherOS support and later removed from existing consoles with a firmware-update that really incited research and development into the PS3 console security, which led to a full break around late 2010 and Sony attempting to retaliate with smear-campaign and prosecution(s) for copyright infringement across the USA and Europe. Some of those were more successful than others.

There have been public emulators for recent consoles from Nintendo and Sony and they've managed to stay up without any cease-and-desist or lawsuits so one would imagine they are doing something correctly to protect themselves (such as not being associated with piracy and some of the shady monetisation involved with that).

PURE GENIUS the photo at the very end showing the gadget connecting a smartphone with an Xbox controller:

https://hoten.cc/images/zc/gamepad.jpg