Furchtbar is a Frankensteinian esolang, stealing ideas from other esolangs for maximized horribleness.
I’ve coded in some esolangs, but never one that’s nondeterministic - seems a nightmare! The design has the hottest paths most likely to degrade so I guess the idea is to have redundancy in your code?
The simple hello-world example is already 2002 lines long, so “production-ready” Furchtbar must be enormous.
Yeah, I guess anything more complex or supposedly useful would need some sort of redundancy for robustness. The easiest way I can think of to reduce data degradation is to enlarge the data array enormously so that the bit flipping is less likely to hit the meaningful data, but that of course is not completely secure.
And of course another thing is to change the direction of code interpretation as often as possible. That’s why the example codes are written in a zigzag manner.
