Nectar is an open-source, next-generation web development language built by Hibiscus Consulting and distributed under the BSL 1.1 License. It is designed to compile entire web applications directly to WebAssembly (WASM), effectively bypassing the traditional, heavy JavaScript-based tooling and runtime ecosystems.

The main features of this language include:

• WebAssembly-First Architecture: Nectar compiles your entire application—including its logic, state, and rendering engine—directly into a .wasm binary. This reduces the role of JavaScript in the browser to a tiny, 10 KB gzipped syscall layer that handles basic DOM updates.

• Zero Node/NPM Dependencies: The language operates with absolutely no package.json, no node_modules, no webpack, and no bundlers. This eliminates the security risks and bloat associated with thousands of nested third-party packages.

• All-in-One Rust Toolchain: A single, self-contained Rust binary handles the entire developer experience, including compiling, formatting, linting, testing, running the dev server, managing the Language Server Protocol (LSP), SSR, and package management.

• Fine-Grained O(1) Signals: Nectar does not use a Virtual DOM, which avoids heavy diffing and reconciliation cycles. Instead, it uses WASM-driven reactive signals to perform O(1) updates, meaning only the exact DOM node associated with a changed binding is updated.

• Web Patterns as Language Primitives: Instead of importing heavy libraries for routine web tasks, common patterns are baked directly into the language as keywords, such as component, store, router, page, form, auth, payment, upload, db, cache, and agent.

• Robust Compile-Time Safety: Drawing heavy inspiration from Rust, Nectar uses a compile-time borrow checker, a static type system, and exhaustive pattern matching to catch bugs before they ever reach production.

• Linear Memory & Zero GC Pauses: By managing state in linear WebAssembly memory, Nectar eliminates Garbage Collection (GC) pauses entirely, providing consistent and highly predictable runtime performance.

• Inherent Security: Cross-Site Scripting (XSS) attacks are made virtually impossible because the runtime does not utilize eval to run code, and user authentication utilizes secure HttpOnly cookies by default.

• Server-Side Rendering (SSR) & Edge Deployment: The identical WASM binary compiled for the client runs on the server using wasmtime. This supports native server-side rendering, hydration, and rapid edge deployments to 29 Cloud Run regions.