> React Flow examples show possible approaches, not production coverage. They omit edge cases, performance considerations, and maintenance paths. Overflow gives you the end result: hardened behavior, documented APIs and types, and components that are ready to ship.
So it's "us" vs. "they"? "They" actually build a very widely adopted open-source solution, why don't you contribute back if "they" omit so much?
National sovereignty is not national pride. Paying company taxes to the 28th regime evicts tax contributions to the company's home nation. Massive German tax money is already today used for non-national interests. EU-inc makes this only worse.
From what I understood, we check whether "snake case category" from step (1) is already known to us (in the cache) so that we need no further processing. So that step (2) and further don't apply for categories that were already produced earlier.
I was tired of writing backend APIs with the only purpose that they get consumed by the same app's frontend (typically React). Leading to boilerplate code both backend side (provide APIs) and frontend side (consume APIs: fetch, cache, propagate, etc.).
Now I am running 3 different apps in productions for which I no longer write APIs. I only define states and state updates in Python. The frontend code is written in Python, too, and auto-transpiled into a React app. The latter keeping its states and views automagically in sync with the backend. I am only 6 months into Reflex so far, but so far it's been mostly a joy. Of course you've got to learn a few but important details such as state dependencies and proper state caching, but the upsides of Reflex are a big win for my team and me. We write less code and ship faster.
Quoting from your other website (linked from OT website): https://www.overflow.dev/
> React Flow examples show possible approaches, not production coverage. They omit edge cases, performance considerations, and maintenance paths. Overflow gives you the end result: hardened behavior, documented APIs and types, and components that are ready to ship.
So it's "us" vs. "they"? "They" actually build a very widely adopted open-source solution, why don't you contribute back if "they" omit so much?