Splitting the public 50:50 lets powerful figures do whatever they want - groups can't coordinate when they disagree on everything. The hack: polarized groups won't block each other's separate actions against shared threats. Instead of seeking consensus, each group can act independently on quiet agreements. Fighting the same enemy separately forces that enemy to split attention - more effective than trying to unite.
@dalias@pkhuong i'm working on fixpoint-iterative primitives lately (as an alternative to structured control flow) that are strictly forward-facing but trivially copyable, and this would be an ideal solution to support time-reversed debugging.
@dalias what.. how is that even logically possible. it needs n iters to reach the beginning of the iteration range. then m iters to go through the range, buffer all results. then another m to go through the buffer in reverse (the actual reverse iteration). space needed is also m.
do you know of a different way to do this? b/c it doesn't seem like 1-step-iterators give us much freedom here.
or do you build an ad-hoc search tree? then the space needed would be log m and m log m makes more sense
i get it now, mysticism. the void is not empty - merely unyielding. you keep the void in mind. much can be revealed, but some will never. so you pick the eternally unrevealable, make it your symbol. your contemplative focus point. something to struggle against, as not to struggle would be to resign to ignorance: resting in what little light you found. a mysticist must reveal. only through revealing they will struggle against the void, first to all that is, second to none.
is the void in the past? is it in the future? yes. i came from it and i shall return to it, having seen all i can see but none the wiser.
can revealing be done efficiently? all it takes is to meet the uncomfortable. this challenge can never be efficient, hence the struggle.
for images of the void, close your eyes or imagine a fully connected graph as its number of vertices increases. think of the void star. the rim of a mandelbrot. there are eight billion images of the void.
ironic that we live in a time where everybody owns a computer with a mandatory button that spawns a supposed "magical genie", except for computer witches & wizards who specifically do *not* have such a button anywhere, nor do they wish to have one
today i'm beginning translating Scopes' internal OOP based system to datalog/database/ECS layout, that is, all pointers become enum-typed indices and object attributes are mapped in arrays.
to begin, i'm writing a small DSL in Scopes to describe the datamodel, and then auto-translate it to C++
phew. five hours later, i've translated *all types* used by Scopes into this format, from which C++ definitions will be derived.
what i like particularly here is that all sub-enums like ICmpKind or TypeKind, and even all error codes, are flattened into the main ValueKind one, but can still be their own enumerator types.
many branch-dependent special cases are now unified this way.
Arts, Maths & Metaprogramming; Game Developer at @duangle. paniq in the demoscene. Building Tukan, a procedural game engine, maintaining Scopes & gently going NowHere. (he/him, they/them)I mostly write in English, rarely in German.Migrated from @paniqMy avatar is the logo of the library I'm working on, a stylized toucan with a four-colored beak.