We Must Talk About: Locality

submited by

Style Pass

2024-11-24 11:00:02

This is a small rant because whenever I see the frontend community talking about state management they always talk in terms of global versus local and that makes me feel a bit left out because I work a lot with thick/rich/fat clients which demands a lot of use of nested localities and I need to have someone to relate to regarding this.

So I'm pitching the entire world to normalize using the words superlocal and sublocal. They refer to something local (as in bound to a particular location, uh... latin: locus), BUT of a bigger and smaller scope respectively.

It gives you a bit more freedom to talk about any relationship in a continuous dimension. "The intersection of Object A and Object B is sublocal to both."

Well, there's a nagging weirdness when using those words. You kinda have to convince yourself that you're talking about sets and sequences when they are only debateably so.

For example, whether a single boolean is a set or not is debatable. You might bring up region of memory, which is discrete, which the thought of helps you convince yourself that a boolean is in a way a set.