I don’t think it’s even about the complexity of use cases, at least for me. If it’s integrated into the foundation of Anytype, meaning you can add basic functions in most areas (inside the document body, as properties, as filters etc.) - and I know this is not an easy task and must be developed in small steps - even if functions are very very basic, this would already resolve highly requested features, and would be a foundation to easily support others that get more complex. An example would be the highly requested self-referencing filters for templates or simply referencing properties (like date) in the title of a note (e.g. for daily notes). Tools like Notion build these features for a very specific audience and specific use cases and I understand that Anytype cannot focus on that. But if it’s part of functions core architecture, then a lot will be possible, even with a tiny and well-testable set of functions.
I feel like Anytype has done exactly this with the Object-oriented approach. They abstracted what really matters in tools like Notion. I fear that if functions are very late on the agenda (and therefore not a core building block for many requests), it will not be a generalized approach like this, but rather a narrow feature that works for 2 or 3 use cases. Then it’s probably still the same workload to get to a level of supporting features that other tools do, in a similar, hacky way.