that what I am saying: if Martin's ideas seem to be unreachable, it is not the ideas, that are flawed, but the code you produced.

as my codes show it is absolute possible and it is simple. Also it is not about "effort". it is about capabilities. I have seen teams struggling literally for years with rather trivial tasks. If instead of trying the ever same failing tactics again they had invested some energy in looking to improve their capabilities and broaden their perspectives, they would had fixed the issues years ago and would be working on much funnier stuff now.

Paul's code does not qualify as an architecture as taught in Computer Science, as it depends on the UI implementation. it isnt modular and there for challenging to test. It does not stop any user to use mutable global state — kicking anything that is useful in OO into the garbage bin.

What ever issues that architecture strives to solve — it only pushes them a little while into the future, they still exist.