Please note: This framework is in active development. I'm keeping it in a cycle of 0.0.x releases at the moment to indicate that it’s not even ready for its 0.1.0. Active work is being done on documentation and features, and APIs should not necessarily be considered stable. At the same time, it is more than a toy project or proof of concept, and I am actively using it for my own application development.

Leptos

```rust use leptos::*;

[component]

pub fn SimpleCounter(cx: Scope, initialvalue: i32) -> Element { // create a reactive signal with the initial value let (value, setvalue) = createsignal(cx, initialvalue);

// create event handlers for our buttons
// note that `value` and `set_value` are `Copy`, so it's super easy to move them into closures
let clear = move |_| set_value(0);
let decrement = move |_| set_value.update(|value| *value -= 1);
let increment = move |_| set_value.update(|value| *value += 1);

// this JSX is compiled to an HTML template string for performance
view! {
    cx,
    <div>
        <button on:click=clear>"Clear"</button>
        <button on:click=decrement>"-1"</button>
        <span>"Value: " {move || value().to_string()} "!"</span>
        <button on:click=increment>"+1"</button>
    </div>
}

}

// Easy to use with Trunk (trunkrs.dev) or with a simple wasm-bindgen setup pub fn main() { mounttobody(|cx| view! { cx, }) }

```

About the Framework

Leptos is a full-stack, isomorphic Rust web framework leveraging fine-grained reactivity to build declarative user interfaces.

What does that mean?

• Full-stack: Leptos can be used to build apps that run in the browser (client-side rendering), on the server (server-side rendering), or by rendering HTML on the server and then adding interactivity in the browser (hydration). This includes support for HTTP streaming of both data (Resources) and HTML (out-of-order streaming of <Suspense/> components.)
• Isomorphic: The same application code and business logic are compiled to run on the client and server, with seamless integration. You can write your server-only logic (database requests, authentication etc.) alongside the client-side components that will consume it, and let Leptos manage the data loading without the need to manually create APIs to consume.
• Web: Leptos is built on the Web platform and Web standards. Whenever possible, we use Web essentials (like links and forms) and build on top of them rather than trying to replace them.
• Framework: Leptos provides most of what you need to build a modern web app: a reactive system, templating library, and a router that works on both the server and client side.
• Fine-grained reactivity: The entire framework is build from reactive primitives. This allows for extremely performant code with minimal overhead: when a reactive signal’s value changes, it can update a single text node, toggle a single class, or remove an element from the DOM without any other code running. (So, no virtual DOM!)
• Declarative: Tell Leptos how you want the page to look, and let the framework tell the browser how to do it.

Learn more

Here are some resources for learning more about Leptos:

• Examples
• API Documentation (in progress)
• Leptos Guide (in progress)

FAQs

How is this different from Yew?

On the surface level, these two libraries may seem similar. Yew is, of course, the most mature Rust library for web UI development and has a huge ecosystem. Here are some conceptual differences:

• VDOM vs. fine-grained: Yew is built on the virtual DOM (VDOM) model: state changes cause components to re-render, generating a new virtual DOM tree. Yew diffs this against the previous VDOM, and applies those patches to the actual DOM. Component functions rerun whenever state changes. Leptos takes an entirely different approach. Components run once, creating (and returning) actual DOM nodes and setting up a reactive system to update those DOM nodes.
• Performance: This has huge performance implications: Leptos is simply much faster at both creating and updating the UI than Yew is.
• Mental model: Adopting fine-grained reactivity also tends to simplify the mental model. There are no surprising components re-renders because there are no re-renders. Your app can be divided into components based on what makes sense for your app, because they have no performance implications.

How is this different from Sycamore?

Conceptually, these two frameworks are very similar: because both are built on fine-grained reactivity, most apps will end up looking very similar between the two, and Sycamore or Leptos apps will both look a lot like SolidJS apps, in the same way that Yew or Dioxus can look a lot like React.

There are some practical differences that make a significant difference:

• Maturity: Sycamore is obviously a much more mature and stable library with a larger ecosystem.
• Templating: Leptos uses a JSX-like template format (built on syn-rsx) for its view macro. Sycamore offers the choice of its own templating DSL or a builder syntax.
• Template node cloning: Leptos's view macro compiles to a static HTML string and a set of instructions of how to assign its reactive values. This means that at runtime, Leptos can clone a <template> node rather than calling document.createElement() to create DOM nodes. This is a significantly faster way of rendering components.
• Read-write segregation: Leptos, like Sycamore, enforces read-write segregation between signal getters and setters, so you end up accessing signals with tuples like let (count, set_count) = create_signal(cx, 0);
• Signals are functions: In Leptos, you can call a signal to access it rather than calling a specific method (so, count() instead of count.get()) This creates a more consistent mental model: accessing a reactive value is always a matter of calling a function. For example:

```rust let (count, setcount) = createsignal(cx, 0); // a signal let doublecount = move || count() * 2; // a derived signal let memoizedcount = creatememo(cx, move || count() * 3); // a memo // all are accessed by calling them asserteq!(count(), 0); asserteq!(doublecount(), 0); asserteq!(memoized_count(), 0);

// this function can accept any of those signals fn doworkonsignal(mysignal: impl Fn() -> i32) { ... } ```

• Signals and scopes are 'static: Both Leptos and Sycamore ease the pain of moving signals in closures (in particular, event listeners) by making them Copy, to avoid the { let count = count.clone(); move |_| ... } that's very familiar in Rust UI code. Sycamore does this by using bump allocation to tie the lifetimes of its signals to its scopes: since references are Copy, &'a Signal<T> can be moved into a closure. Leptos does this by using arena allocation and passing around indices: types like ReadSignal<T>, WriteSignal<T>, and Memo<T> are actually wrapper for indices into an arena. This means that both scopes and signals are both Copy and 'static in Leptos, which means that they can be moved easily into closures without adding lifetime complexity.