Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

State of the project — inactive #368

Open
samuelcolvin opened this issue Nov 21, 2024 · 2 comments
Open

State of the project — inactive #368

samuelcolvin opened this issue Nov 21, 2024 · 2 comments

Comments

@samuelcolvin
Copy link
Member

TL;DR this project is on hold while the Pydantic team is flat out building logfire and continuing to maintain Pydantic.

We use FastUI internally for the admin interface of Logfire, and it works well for that application, but we don't have a strong impetus to invest heavily in improving FastUI.


Some background: I originally built FastUI in the hope we could use it for some user facing functionality in Logfire, that didn't happen for a bunch of reasons:

  1. FastUI wasn't ready when we needed to build that stuff
  2. There isn't enough repetitive CRUD functionality in Logfire to demand the truely reusable/composable component structure that FastUI tries to provide.
  3. There was some complex use of generic unions we needed in Pydantic before arbitrary components would work in FastUI, which slowed us down.

Ultimately I couldn't persuade our frontend team that FastUI was the right tool to use, and I wasn't prepared to force them to use a tool I was still experimenting with.

Also, as per #48 I would really like the rendering of HTML in FastUI to happen exclusively (or mostly) serverside, but that's a big rewrite that I don't have time to work on right now.

I won't mark this repo as archived so discussions can continue, and we can continue to fix any bugs we find. But don't expect new PRs or issues to receive attention from the Pydantic team.

For those who were excited about FastUI, sorry to disappoint. 🙏

Maybe at some point in future I'll have the time and bandwidth to resume the project.

@samuelcolvin samuelcolvin pinned this issue Nov 21, 2024
@samuelcolvin samuelcolvin changed the title State of the project State of the project — inactive Nov 21, 2024
@fmrib00
Copy link

fmrib00 commented Nov 23, 2024

Such a pity! but thanks very much for your hard work on such a useful package, which I have been using heavily and successfully in my real-life project!

@Zaubeerer
Copy link

Thanks for the honesty and clarity!

Maybe there is a group of developers that would like to pick up the work?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants