MCBE needs predictable redstone ticking based on relative position!

MC: Bedrock Edition

Has randomized ticks that break a lot of redstone builds by making them work in a very chaotic way that causes them to fall apart.

MC: Java Edition

Has a bug known as "locational redstone" that is caused by the fact that Java is single-threaded, causing it to only register one sub-chunk of ticking at a time before moving on to the next in a predictable fashion. This is a glitch that was removed on Bedrock because Bedrock is where Mojang wants to go with Minecraft- and not even REMOTELY where the original Java and general technical communities want to go.

Creating a middle ground:

Create an optional relative-positional redstone system for at least Bedrock Edition. I imagine this being a little different than Java's "positional redstone", as this feature could use the redstone-related block's position relative to the other redstone-related blocks instead of XYZ position to determine which part of the contraption ticks first. While this feature may be hard for players to calculate and build around, it at least adds some order to Bedrock redstone ticking, and will most likely satisfy the technical community to some extent.