Show HN: Nova JavaScript Engine https://ift.tt/FUV0ywM

Show HN: Nova JavaScript Engine We're building a different kind of JavaScript engine, based on data-oriented design and willingness to try something quite out of left field. This is most concretely visible in our major architectural choices: 1. All data allocated on the JavaScript heap is placed into a type-specific vector. Numbers go into the numbers vector, strings into the strings vector, and so on. 2. All heap references are type-discriminated indexes: A heap number is identified by its discriminant value and the index to which it points to in the numbers vector. 3. Objects are also split up into object kind -specific vectors. Ordinary objects go into one vector, Arrays go into another, DataViews into yet another, and so on. 4. Unordinary objects' heap data does not contain ordinary object data but instead they contain an optional index to the ordinary objects vector. 5. Objects are aggressively split into parts to avoid common use-cases having to reading parts that are known to be unused. If this sounds interesting, I've written a few blog posts on the internals of Nova over in our blog, you can jump into that here: https://ift.tt/kONzZMu https://ift.tt/UrdEOBa November 18, 2024 at 02:07AM