skulski at pas.rochester.edu
Sat Jul 25 07:30:02 CEST 2020
thank you for the explanations. I posted them on the Emulators web page near the end.
From: Oberon [oberon-bounces at lists.inf.ethz.ch] on behalf of Michael Schierl [schierlm at gmx.de]
Sent: Friday, July 24, 2020 5:56 AM
To: oberon at lists.inf.ethz.ch
Subject: Re: [Oberon] [EXT] Re: Emulators
Am 24.07.2020 um 07:29 schrieb Skulski, Wojciech:
> There are two versions, with Webassembly and without. The one with WA seems to be more compact.
I'd say they are roughly on par. You may have been confused by the fact
that the CPU code in the webassembly version is split among two files
(the JS source which is ~140 lines and the Webassembly source which is
~300 lines), while the CPU code in the pure JS version is in one file
All other code is the same, WebAssembly does not really have any
benefits in emulating the screen or the other peripherals.
For executing the WebAssembly version in the browser, you need to
compile the WebAssembly source code, which results in about 2.5KB of
compiled wasm. So the pure JS version is easier to modify since you do
not need to compile it if you change anything.
In case you are referring to the download size for the user, the WASM
version is about 5KB less, which roughly matches the difference of the
WebAssembly source size and the compiled WebAssembly size. But
negligible if you take the size of the disk image into account.
More information about the Oberon