3 ms·

Early games frequently took the approach of inventing an interpreted machine code in which the bulk of the game would be written, with an assembly interpreter t

by codebje 7mo ago

Early games frequently took the approach of inventing an interpreted machine code in which the bulk of the game would be written, with an assembly interpreter that would need to be rewritten for each target IA and modified for the specific peripheral mixes of each target machine. The approach runs slower than a game written directly in assembly, but the cost to port to different architectures is much lower. Sort of like Electron trades off native performance and look-and-feel to make multi-platform apps much more achievable. IMO the OS vendors failed everyone by refusing to even attempt to agree on a common API for UI development, paving the way for web browsers to become the real OS and, ultimately, embedded browsers to be the affordable and practical way to be cross platform.

paulryanrogers 7mo ago
Except the OS's don't even ship a consistent enough browser engine. (Standards be damned.) So apps ship their own browser over and over again.
- zadikian 7mo ago
  Yeppp. Is there no way for Electron apps to use a shared engine if one is available?
  - paulryanrogers 7mo ago
    I think Tauri tries this approach.
  - edflsafoiewq 7mo ago
    Of course. Arch for example ships packages that use a shared system electron. But you'll often end up need multiple electron versions. There's also stuff like lorca which shells out to an installed Chromium browser.
  - c01nd01r 7mo ago
    https://neutralino.js.org/ https://neutralino.js.org/ But I think even there it’s possible to encounter platform-dependent bugs - starting from view issues (you know, different OS can use different browser engines) and up to those related to system APIs.
- pjmlp 7mo ago
  And then you guys complain about Google taking over the Web!?!? Go figure what would happen when Chrome gets shipped everywhere, because writing browser agnostic code is too hard.
Geof25 7mo ago
Exactly what .NET does with MAUI, just little bit lower than electron

by codebje 7mo ago

paulryanrogers 7mo ago

Except the OS's don't even ship a consistent enough browser engine. (Standards be damned.) So apps ship their own browser over and over again.

zadikian 7mo ago
Yeppp. Is there no way for Electron apps to use a shared engine if one is available?
- paulryanrogers 7mo ago
  I think Tauri tries this approach.
- edflsafoiewq 7mo ago
  Of course. Arch for example ships packages that use a shared system electron. But you'll often end up need multiple electron versions. There's also stuff like lorca which shells out to an installed Chromium browser.
- c01nd01r 7mo ago
  https://neutralino.js.org/ https://neutralino.js.org/ But I think even there it’s possible to encounter platform-dependent bugs - starting from view issues (you know, different OS can use different browser engines) and up to those related to system APIs.
pjmlp 7mo ago
And then you guys complain about Google taking over the Web!?!? Go figure what would happen when Chrome gets shipped everywhere, because writing browser agnostic code is too hard.

Geof25 7mo ago

Exactly what .NET does with MAUI, just little bit lower than electron