{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiglmhb2in7vm6p5vnpvf5l2nauokmnults27iarbugqwh6d5cx644",
    "uri": "at://did:plc:25rdn5elo5izoxrmtis34zuk/app.bsky.feed.post/3mpcuh5uv2fd2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreic2cl6aw4ctgkrwkmmn45h72vw7ehzpx3kxakhunq4ertnbededvq"
    },
    "mimeType": "image/webp",
    "size": 71778
  },
  "path": "/hamdymohamedak/nyra-memory-safety-of-rust-with-the-simplicity-of-js-2p66",
  "publishedAt": "2026-06-28T01:21:20.000Z",
  "site": "https://dev.to",
  "tags": [
    "javascript",
    "programming",
    "rust",
    "showdev"
  ],
  "textContent": "Nyra – Memory safety of Rust with the simplicity of JS\n\nHi,\n\nI built Nyra because I love the memory safety and fearlessness that Rust’s ownership model provides, but I often missed the development speed and clean, expressive syntax of JavaScript/TypeScript.\n\nKey Features:\n\n\n    Rust-like Ownership: Compile-time memory management without a garbage collector.\n\n    JS-inspired Syntax: Minimalist, familiar, and easy to read.\n\n    Optional Typing: Types are optional. The compiler uses aggressive type inference where possible, allowing for a dynamic feel while maintaining performance and safety under the hood.\n\n    LLVM Backend: Compiles down to efficient machine code.\n\n\nThe project is still in its early stages, and I'm heavily working on the compiler design. I would love to get your feedback on the syntax, the architecture, and how to handle the edge cases of static ownership with optional typing",
  "title": "Nyra – Memory safety of Rust with the simplicity of JS"
}