{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreibzdd5ub2tavqabrqr2by2ruzqclme3tkiaxv2cmald36gbffvviy",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mnp7wpcvar42"
  },
  "path": "/t/idea-light-weight-rust-as-zero-build-scripting-language-with-jit-runtime/24377#post_6",
  "publishedAt": "2026-06-07T11:27:53.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "Though perhaps possible, creating a performant Rust interpreter like `rust-repl` would likely take years of effort, and I doubt that enough volunteers are available and willing to make that happen.\n\nAnd I specify “volunteers” because most people who contribute to Rust do so for free AFAIK, and if none of those people are interested in a particular feature, it can easily languish for years without progress. There’d probably have to be a _lot_ more demand or commercial support in order for people to spend years making an performant interpreter, when there’s so many other goals for the Rust project in higher demand.\n\nNote that we do already have a Rust interpreter called Miri. However, it runs code around 100-1000x slower than the compiled program, because the primary intent of Miri is to be used for **testing** code, not running full-fledged programs. (It’s not a JIT or anything.) You wouldn’t get the fast iteration of JS/TS from using Miri; the part where the code _runs_ would become the bottleneck.",
  "title": "Idea: light weight rust as zero build scripting language with JIT runtime"
}