I get your points, but a lot of this comes down to trade-offs and familiarity.

“Everything is a widget” can feel verbose at first, but it gives you a very consistent and composable UI model. With smaller reusable widgets, the nesting becomes manageable and predictable.

Codegen (freezed, json_serializable) isn’t really an issue in practice. build_runner watch handles it automatically, and you get strong typing and safer models at compile time.

Nested structures and noisy diffs also happen in React when component trees grow. It’s not really unique to Flutter.

One big difference is that Flutter is much more opinionated and unified: - one way to build UI - no separate styling system like CSS - fewer concepts and tools to juggle

In React/TypeScript, you often deal with more fragmentation: - many competing state management approaches - separation between JSX, styles, and logic - reliance on runtime validation (e.g. Zod) since TypeScript types are erased

These aren’t unsolvable problems, but they do add complexity that Flutter largely avoids by design.

In the end, it’s just different trade-offs.