https://github.com/SLaks/Silon/blob/gh-pages/styles/basic-ga...
It makes for a cool demo of how simple Boolean circuits work, but you can't really say it's "doing computation" in CSS when all of the actual computation has been done ahead of time.
Still, it's clever.
https://github.com/SLaks/Silon#implementation-details https://github.com/SLaks/Silon/blob/gh-pages/styles/_operato...
The actual declarations end up being nicely simple; see https://github.com/SLaks/Silon/blob/gh-pages/styles/_themed-...
The CSS is just a truth table, but the LESS (which is Turing-complete) actually contains all of the logic.
As someone who works with CSS everyday, it's exactly what I expected once I saw it working. How else could it possibly work?
This project doesn't use rule 110, it uses LESS which sorts out the logic while compiling and spits out the results in css.
This is actually an important lesson that is often missed: if the app you're writing gives the anonymous users any kind of find/replace macro capability, you're giving them a fully Turing complete language (though it's probably not easy, but that rarely stops anyone) and all the potential problems that can bring.
I get shivers just thinking about all the fun I can have breaking web semantics this way.
o.o am i doing it??
Of course, this being the web you’re somewhat limited in browser support: http://caniuse.com/#feat=css-variables
I didn't realise you could click on them until after a good while though.
