If you can't know the order of your static class init routines' execution, you can't create some kinds of software systems, where such information must be known beforehand. Failing that we have to contrive our own init workflow launched from a single point of entry, instead of using something intrinsic for the guarantees we need. What that means is that this advanced feature of the programming environment should be avoided in certain cases, making it useless and (IMO) to be avoided.

I was asking about programming environments that facilitate certain kinds of clean init semantics.

Like a clock. Or something that is operationally clocklike, deterministic, like we should design and implement our software to be in terms of reliability.