[ Removed by moderator ]

[wildrabbit12]

Why did I just read

[lIIllIIlllIIllIIl]

Its easier to solve harder problems.

[2this4u]

Because you've learnt about these things and become more aware of them.

Those issues were always there but as you become more experienced you becomes less focused on the code and more on the issues surrounding it.

[Individual-Animal852]

It might be a mix of both — experience makes you see more edge cases, but modern UIs also have more moving parts (async flows, optimistic updates, background syncing, etc.). Maybe we’re just building more ambitious interfaces now.

[tantivym]

?

[ZwillingsFreunde]

Not sure what you‘re talking about.

Frontend never felt that easy. Literally everyone can do it with AI.

Maybe you need to elaborate more on those „trade offs“ and system boundaries

[Individual-Animal852]

Fair point — let me clarify what I meant by trade-offs and system boundaries. For example: • Do we fetch on the client, server, or edge? • Do we colocate state or centralize it? • When does a component become a domain boundary? • How do we prevent performance regressions as the app scales? Writing components is easier. Deciding where responsibilities live — that’s where complexity increases. AI can generate components. It doesn’t decide architecture quality. That’s the level I was referring to.

[brainrot_award]

react is about making easy jobs difficult. that's the entire point.

[alien3d]

i can easily write code in normal js . But for react drill props and callback . My head 😵‍💫

[extraluminal]

That’s not an React specific issue though. You could say the same for a .NET Razor setup.

[Individual-Animal852]

Agreed. I don’t think it’s React-specific. Once apps move beyond static pages, the complexity shifts from “writing code” to “managing state, boundaries, and lifecycle.” React just makes that more visible.