I’m not sure that the distinction between “element-wise” and “group-wise” mindsets are mutually exclusive in the design space for a language. The set of progra

I’m not sure that the distinction between “element-wise” and “group-wise” mindsets are mutually exclusive in the design space for a language. The set of programs that can express problems as transformations on arrays is quite large. But I think there’s a large overlap with programs that also need to manage resource lifetimes as well where a resource could be a region of foreign-allocated allocated memory, a database connection, etc; a process-scoped object that can only be acquired (or not) at runtime. Even in Odin you’re going to need to think in terms of arrays and how individual element lifetimes at some point depending on how you classify and structure data. The trade off seems to be that how you specify and maintain contracts for the lifetime of objects like sockets and handles are up to you and Odin won’t help you with that. In return you get array oriented initialisation? Or am I misunderstanding the mental model?