Skip to content

Migrate core to rust and maintain TS plugin api (Deno) #9

Open
@john-bv

Description

@john-bv

Questions & Answers

Why?

Rust is fast, and allows us to practice better memory practicing, allowing us to write efficient code with incredible speed.

So will the Deno Typescript code be discarded?

I plan on keeping a maintained branch with a similar api to the incoming changes for the rust version; this is because I am not set on removing the TypeScript version, as I think it would be a good reference for benchmarking the rust version, as well as offering an opportunity for more people to contribute to it.


Plugin API

While the core code will be migrated to rust, we will still be using a TypeScript plugin API integrated with Deno. The plugin API will be isolated, meaning each plugin will run in it's own "context" to allow full usage of Deno's "secure by default" motive as well as better control of developing and debugging plugins.

Please only use this issue for reporting issues with this change itself, for discussions refer to: #8

Metadata

Metadata

Assignees

No one assigned

    Labels

    API BreakBreaks the APICoreA core related issue or PRDocumentationImprovements or additions to documentationFutureThis issue or PR is something that will be added in the future.

    Type

    No type

    Projects

    Status

    To do

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions