unicode-proposals VS ioccc-obfuscated-c-contest

Because... not wanting to have to deal with racism? News flash: There's no official ISO 3166 code for a confederate flag, regardless of IOS or Android. You're not typing one.

You mean the "Cool S", right? Well, the standard for encoding text (and emoji) on computers is Unicode - they have a list of selection factors for what make good emoji candidates. The Cool S, sadly, doesn't seem to fulfill the requirements, being an exact image (instead of a representation of a broad concept) and not having any sort of apparent use. It might fare better as a non-emoji symbol (like 🗫), those seem to have less strict requirements. In any case, I can't find any evidence that somebody's gone to the effort to write up a full proposal, just this somewhat half-hearted suggestion from 2018.

Source: https://github.com/Crissov/unicode-proposals/issues/256

Soviet flag emoji proposal

I see lots of misinformation following this about copyright and fonts. In the United States, fonts are copyright-able as programs but not as letterforms. You cannot copyright the basic elements of language, so anyone can make his own executable program (i.e. a font file) that has literally any glyph in it without infringing on copyright. Note that some things that we make think of as glyphs (e.g. the recycling sign or the textile care symbols) can be trademarks and protected under that class of intellectual property law.

There's more proposals here:

https://github.com/Crissov/unicode-proposals/issues/

There's a rather whimsical one proposed called the Priest Emoji!

https://github.com/Crissov/unicode-proposals/issues/425

Instead of having proposals, why not just implement every thing/subject/object we can think of?

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.