realworld VS fastapi-realworld-example-app

In light of all this, it became exceedingly clear that someone else needed to step in and help. Why not me? Well, it can be me. And, after 3 months of development, I am happy to announce (again) dwayne/elm-conduit (demo), an open-source Elm SPA for RealWorld's Medium.com clone.

https://github.com/gothinkster/realworld

It's just for web app (a Todo app). Your GIS AND CLI ideas are interesting, I haven't seen anything similar to realworld for those.

View on GitHub

So what would be a better benchmark? Perhaps a "standard" "real world" app, like https://github.com/gothinkster/realworld

Or something simpler?

RealWorld example app is a full-stack application called "Conduit" that consists of a backend that serves JSON API and a frontend UI. There are numerous implementations for different languages and frameworks, but in this tutorial you will be using the Spring backend and the React frontend.

Github has millions of projects, some large fraction with more than 100 stars, so it doesn't seem like you are searching very hard. But more importantly, why "100 stars"? Stars are meaningless and arbitrary. Many developers use stars like bookmarks. I just did a quick search and noticed a project like realworld (just a demo for learning, 65 contributors) has have more stars than Bitcoin (900+ developers, perhaps you have heard of it?)

I feel you, context API sometimes overcomplicates everything. Let me introduce to you RealWorld. It is a great project that uses composition to make its structure scalable. It is actually a codebase that implements various fragments of a larger scale project such as Medium or Twitter. Check it out here: https://github.com/gothinkster/realworld. I hope this helps!

I'd also recommend checking out various "real world" repositories. E.g. one for FastAPI is here It comes with perfectly reasonable API.

Me showing off Okapi (hopefully): Okapi is simple. A functor can do this, applicative can do this, a monad can do this. Learn this small set of functions. Sequence them with do. Branch them with <|>. You need to learn the structure of an HTTP request, but that's good because you need to know that anyway if you want to develop Web apps. Here's the documentation. Look at how simple and compact this is compared to this.