Previous submissions with significant discussion:
- https://news.ycombinator.com/item?id=18991404
- https://news.ycombinator.com/item?id=16218872
- https://news.ycombinator.com/item?id=12372242
Previous submissions with significant discussion:
- https://news.ycombinator.com/item?id=18991404
- https://news.ycombinator.com/item?id=16218872
- https://news.ycombinator.com/item?id=12372242
https://news.ycombinator.com/item?id=18992556
>The mov-only DOOM renders approximately one frame every 7 hours, so playing this version requires somewhat increased patience.
https://github.com/xoreaxeaxeax/movfuscator/tree/master/vali...
I have to say, reading through the github for the movfuscator was pretty damn amusing. I honestly burst out laughing at the control flow graphs. But I'm curious, is this actually practical for anything?
Running Doom at 1 Frame per 7 hours is, pretty unreasonable. Would text based software even be usable with this?
Either way, I do enjoy cleverly, overly engineered, possibly useless things created just because someone thought it would be funny.
Also, a chunk of code that is just a long string of MOV instructions is going to be really easy to spot for an antivirus program.
As someone else noted, a large block of mov instructions would be quite easy to spot so you'd have to tie it into a bit of core application / algorithm logic. But that doesn't mean the whole program needs to be written that way.
What about a one-time screen kindly asking for a donation?
Yes? Obviously?
> What about a one-time screen kindly asking for a donation?
If it doesn’t have a “don’t show this again” checkbox, then I would have to say “yes”.
I liken the motivations behind things like Movfuscator to mountain climbing: they do it because it's there to be done.
I just wrote a quick C program to find the primes less than 100000 and compiled it with gcc and movcc. I wouldn't say it's, you know, fast, but I'm impressed at how it does finish in an amount of time that I was willing to wait.
$ time ./primes.gcc | wc -l
9592
real 0m0.035s
user 0m0.031s
sys 0m0.012s
$ time ./primes.movcc | wc -l
9592
real 0m10.511s
user 0m8.289s
sys 0m2.228s
It looks like the reason that it spent so much time in syscalls is that it somehow uses signals for control flow. (I'm not quite sure how that works.)see https://github.com/xoreaxeaxeax/movfuscator/blob/master/movf... and https://github.com/xoreaxeaxeax/movfuscator/blob/master/movf...