sparklines VS ioccc-obfuscated-c-contest

`sparklines`[1] is good for an overall low-res view. `termgraph`[2] is sometimes better for a higher-res, more capable view (but can be finicky about the data.)

[1] https://github.com/deeplook/sparklines

[2] https://github.com/mkaz/termgraph

A semi-automated system that compares old unsafe code to new unsafe code would likely be really helpful here - say, a LLM prompted to investigate whether the new unsafe blocks are a significant difference in scope and documented intent from the old unsafe blocks. Unless the winners of https://www.ioccc.org/ are among your attackers, it's a pretty solid line of defense.

For that you can go savor the archives of IOCCC : https://www.ioccc.org/

>> Perl can also be hilariously unreadable: https://www.foo.be/docs/tpj/issues/vol4_3/tpj0403-0017.html

Most programming languages can be obfuscated. That does not mean people write code in those programming languages like that:

C: https://www.ioccc.org/

Javascript: view-source:https://www.google.com/

The truth is that insulting Perl is considered stylish by some, so many people do despite knowing little to nothing about Perl and having never used it.

If you want the most complex, then probably here https://www.ioccc.org/

Since someone already linked Enterprise FizzBuzz, I'll link The Obfuscated C Contest as a possible source of inspiration.

Or this one [3] that calculates pi by estimating its own surface area.

Or this one [4]. It's a lovers quarrel, written simultaneously in C and English. It's incredible, seriously, read it.

[0]: https://www.ioccc.org/

I wonder what sort of "English" it spits out when fed obfuscated C code

OP is going to rage quit when he sees https://www.ioccc.org/

I mean, its no https://www.ioccc.org/ entry

The International Obfuscated C Code Contest for all you brain damage needs.