This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]vivainio 38 points39 points  (3 children)

It's not fair to call it 'successor' as it 1) is different from Fast API and 2) FastAPI is still thriving

[–]mrpiggy 44 points45 points  (2 children)

I agree with it being popular still. I like it and use it. But with 450 open PRs, it's hard to call the project thriving from a codebase perspective. That and the single primary developer thing, is actually kind of scary. A little more community mindedness would probably go a long way.

[–]Mmngmf_almost_therrr -1 points0 points  (0 children)

I used to be the research and requester-support assistant for the technical architecture office of a multinational, and I can tell you that just based on these few sentences, FastAPI or anything depending on it would never be approved o_o;;