Skip to content

Implement JS engine from scratch #71

@Singtaa

Description

@Singtaa

This applies to OneJS V3 or later.

PuerTS covers way too much ground. It supports multiple JS backends, extra platforms like Harmony and Weixin, plus both Unreal and Unity. On top of that, their codegen and emscripten bits are pretty hard to tweak and maintain.

For OneJS, it makes more sense long-term to keep it Unity-only. Since QuickJS is barely maintained these days and falls short compared to V8 (aside from smaller builds), it’s better to just stick with V8. That way we save time for both devs and users.

That said, PuerTS has a ton of solid work around interop (glue code), optimizations, and overall workflow. Replacing all of that is going to be a huge effort.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    Status

    Long Term

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions