A big challenge: Enabling separation of concerns (UI/logic) for beginners

I'm seeing it's a common theme, especially in the Python community, to implement tightly coupled UIs and business logic. It's done in the name of convenience, but inevitably backfires once you go past trivial applications.

I've lived the whole evolution of web-based applications, back when CSS didn't exist and PHP was something added to HTML to make it "dynamic". I'm glad web development has evolved; I think everyone is. But why do we have to go back to it, repackage it as something cool and make the same mistakes?

I understand it's appealing to those whose title isn't "software engineer", because MVC can be a pain. Should it be though?

I'm working in this space, building a state-driven half no-code/half Python framework , but rather than driving more attention to it I'd like to discuss the premise.

Is this a battle worth fighting? Or am I making a big deal out of something no one cares about?