runtime

Discussed in nodejs/node#40443

We can build much smaller Mono runtime for .NET Core purposes by simply removing code we don't need in this configuration. We did a few easy initial steps but we can go much further.

This list is not comprehensive but parts like

• Culture Data
• Any PAL related code
• Unused icalls

• Source

JsPointerToString(NULL, 0, &str);

• Expected
  str = empty string

• Actual
  failed and returns JsErrorNullArgument

I think this should be possible

In bytecodealliance/wasmtime#2497 (comment) we added support for generating nested modules, and we generate these modules by concatenating strings of WAT and then passing it to Module::new which internally checks for WAT strings and assembles them into Wasm bytes if necessary.

We can make this more efficient, improving the number of test cases we fuzz in a

We should add cmdlinetest for -XX:[+/-]UseCompressedOops. See the recent issue eclipse-openj9/openj9#13561

Similar to existing cmdlinetests that we have https://github.com/eclipse-openj9/openj9/blob/master/test/functional/cmdLineTests/xxargtest/XXArgumentTesting.xml

Tons of good improvements that can be made to the codebase:
https://deepsource.io/gh/elsaland/elsa/issues/?category=recommended

If a new Environment is created, processes inside of it will not have access to any command line arguments or environment variables by default. They need to be added to the ConfigEnv struct from which the Environment is created. Currently this is only possible from the host, but is not exposed as a [host function

With #235 I've noticed that InstanceOf is undocumented in the readme.

Add a dark/light mode switch in the menu.
The semantic-ui framework already handles that.
The thing is to also change the plot background color when in dark mode.