IssueRaiser

Status Update - May 2026

I wanted to provide a short update on the current state of Leptos development, so that people have an accurate understanding of where things are currently. **tl:dr;** Leptos is not abandoned but will be lightly maintained going forward. I consider it feature-complete and do not expect to do significant new development in the future. I am open to additional maintainers who want to take a more active role. ### Background I created Leptos as an experiment and personal project, at a time when I was learning Rust and was very interested in using it for web applications. It's been successful for that purpose! It's also been much more popular than I would have expected at that time, in part thanks to the publicity it received very early on from several developers with very large online followings. Working on an open source project that has users is fulfilling, but it can also be draining over time. It's fun to interact with people, but it's tiring to answer the same questions year after year. It's interesting to work on new features and solve big problems, but—especially once a project has reached maturity—it's exhausting to deal with dozens of niche issues. The rise of LLMs and of coding agents has really fundamentally changed the cost-benefit analysis on this for me. Over the last year or so I've found that the volume of meaningful community conversation and engagement has declined significantly. Over the last few weeks I've experienced a new and sad problem first-hand: the

Posted by gbj on May 8, 2026, 4:48 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments

pricing (EdTech)

Status Update - May 2026

gbjMay 8, 2026, 4:48 PM

I wanted to provide a short update on the current state of Leptos development, so that people have an accurate understanding of where things are currently. **tl:dr;** Leptos is not abandoned but will be lightly maintained going forward. I consider it feature-complete and do not expect to do significant new development in the future. I am open to additional maintainers who want to take a more active role. ### Background I created Leptos as an experiment and personal project, at a time when I was learning Rust and was very interested in using it for web applications. It's been successful for that purpose! It's also been much more popular than I would have expected at that time, in part thanks to the publicity it received very early on from several developers with very large online followings. Working on an open source project that has users is fulfilling, but it can also be draining over time. It's fun to interact with people, but it's tiring to answer the same questions year after year. It's interesting to work on new features and solve big problems, but—especially once a project has reached maturity—it's exhausting to deal with dozens of niche issues. The rise of LLMs and of coding agents has really fundamentally changed the cost-benefit analysis on this for me. Over the last year or so I've found that the volume of meaningful community conversation and engagement has declined significantly. Over the last few weeks I've experienced a new and sad problem first-hand: the

Comments (0)

No comments yet. Start the discussion.

Comment on this issue