Instead of destroying the universe, can we destroy prior, failed shuffle/check iterations to retain o(1)? Then we wouldn’t have to reload all of creation into RAM.
Instead of destroying the universe, can we destroy prior, failed shuffle/check iterations to retain o(1)? Then we wouldn’t have to reload all of creation into RAM.
Reminds me of the Reboot hotel offices.
A cluster duck, if you will.
Can we call communities “lemlets?”
Exactly what I do, too! (Tho I use VS Code and owncloud on desktop, and foldersync on Android.) Only issue I have is occasional file conflicts, if some edits didn’t get sync’d right away. (Tho it hasn’t happened recently, perhaps due to Zettel’s recent file saving updates.)