4 ms·
If we took out the Javascript layer we'd be down to C, right? We've had emulators written in portable C for nigh on twenty years. Where's the challenge in that?
by mechanical_fish 15y ago
If we took out the Javascript layer we'd be down to C, right? We've had emulators written in portable C for nigh on twenty years. Where's the challenge in that? ;)
The advantage of JS as a runtime environment is that it's got the most extensive cross-platform app ecosystem in the world, with a lot of eyeballs on it. Every new difference that arises between the behavior of a JS engine and that of its peers is greeted by a hundred thousand screams from the mouths of a hundred thousand web developers.
Plus, I believe the pain required to get your app to run in all the popular JS engines is mild when you compare it to the ins and outs of cross-platform C libraries.
- MostAwesomeDude 15y agoActually, no, beneath the JS layer is the browser, which is a massive wall of architecture-independent C++ with its own graphics abstractions and high-level constructs. You'd need to drop another level or three to reach the C layer. I dare you to actually try SDL sometime; it is far less pain than doing browser work in JS.