x86CSS is a working CSS-only x86 CPU/emulator/computer. Yes, the Cascading Style Sheets CSS. No JavaScript required.
What you’re seeing above is a C program that was compiled using GCC into native 8086 machine code being executed fully within CSS.
↫ Lyra Rebane
Hand-written CSS, no JavaScript, and effectively no HTML.
Wizardry.
Am I the only one whose reaction to this is not just, Hey cool? but also, How on earth did CSS end up turning into a literal Frankenstein’s monster, a static lump of material that somehow manages to be “alive” and thinks??
You are absolutely NOT the only one. This feels just wrong on so many level.
Although I want to send kudos to Mr. Frankenstein.
Andreas Reichel,
HTML was supposed to be “content” language”,
CSS and “presentation” one,
and JavaScript the “behavior”
They have now mixed all of these. It started with “hacks” like table based designs and later finely tuned divs, which should have never been part of HTML
There was a short lived effort to bring back semantic tags, like “this is an emphasis”, “this is a navigation block”, which also fell short.
Now CSS has gone full “villain” mode, and embraces turing completeness
Basically the only “sane” technology left is JavaScript, and that is because it still focuses on its job, and does not (usually) step on others’ toes
But we need MOAR FEATURES! COMPLEXITY MUST GO UP… Ĉ̸̢̨̕O̵͙̅͝M̷͖̿P̴̲̓͜L̶̩̾Ė̵̼̭͗X̴̨̺̿͒İ̷̧͇̕T̶̗̞̒Y̴͈̐͋ ̶̲͓̔͝M̸̠̅U̴̱̱̕S̴͐͜Ţ̷̬̾ ̴̢͛͋Ġ̴̪Ó̶̗͇͛ ̵̮̙̿̿Ú̶̜͋Ṗ̵̤͠
@sukru,
I always appreciate your content, but
You lost me here. The only “sane” technology in my opinion is WebAssembly and XML. JavaScript was born from unholy incest …
I am willing to give JavaScript some credit in that it was always meant to be a Turing Complete programming language and was always meant to be used for scripts, so a well-designed website should work with scripts disabled (for stuff that doesn’t need scripting), CSS being Turing Complete is a much worse Eldritch horror,
In a Firefox-browser comes this message:
“Your browser does not support the CSS features required to run this demo. Please try with an up-to-date Chromium-based browser. Why? (hide message)”
Almost as if Firefox is a saner browser , and uses Cascading Style Sheets , as, um , style sheets only .. ?
I think I’ll stick to my Firefox for now, thank you very much.
there is a lot of stuff that Firefox does not implement, because they think it’s just not worth the risk, but are available in chrome
e.g.:
https://mozilla.github.io/standards-positions/#web-bluetooth
https://mozilla.github.io/standards-positions/#webusb
interesstingly enough, they’re just shipping WebSerial
https://mozilla.github.io/standards-positions/#webserial
So CSS as another badly not needed attack vector to make us miserable .
“Hey , we disabled Javascript but this thing came through 0-day in Chrome CSS engine”
This, again.