A concrete slab is a basic building block of a pavement, but it's not particularly useful or appropriate for a wristwatch.
I think there's a gap between what you're trying to solve and what you think you're trying to solve, and that's giving a massive impedance mismatch between what you're trying to do and how you're trying to do it.
How would you go about allowing the user to enter and store data at runtime without knowing the size of the data in advance then? I don’t agree with you at all. A variable amount of data that can change at runtime is universal across all programs. This isn’t something specific to a certain coding style
