I think it’s important not to reduce readability of Java code, introducing a new pattern into the mix would go against that.
I think most developers using Vaadin Flow, do not want to be (or are not) experts in Vaadin, they want to be (or are) experts in Java, so they would feel more comfortable if Vaadin followed common patterns, rather than invent their own.
The best thing we can do, is not to make them think about “how do I do this best in Vaadin”, but them just doing it, because its familiar.
It would be beneficial even for junior Java developers to be able to look at Vaadin code and understand it, and to be able to fix a bug they got assigned.
Similar to how lambdas and method referenced scared and confused me initially, I think this pattern would produce similar results, since that’s not something you really learn anywhere, or rather - if you learn, you learn no to do it. Especially since its not something that is widely being adopted in the industry (as far as I’m aware) unlike lambdas / method references.