I realy hope an AI did this intead of human, such a waste of time (the css part, not the x86)
Show HN: X86CSS – An x86 CPU emulator written in CSS
21–30 of 99 posts
Re: Show HN: X86CSS – An x86 CPU emulator written in CSS
#22> Your browser is unable to run this demo. Please try with an up-to-date Chromium-based browser. Sorry to see internet regressing to Internet Explorer days. Edited to add: This is the message I get when using Firefox.
For what it's worth Firefox has a bug open to implement some of the core CSS features being used here: https://bugzilla.mozilla.org/show_bug.cgi?id=1950366
Re: Show HN: X86CSS – An x86 CPU emulator written in CSS
#23There is absolutely no reason for css to be turing complete. None. That being said, well done
Can an argument be bade that CSS only exists becuase javascript failed to develop a styling component to displace it? I like to think webassembly is the right track. But ECMAScript and CSS alike need(ed) to devolve into a simpler byte-code like intermediary language syntax. Browsers supporting complex languages has always been a bad idea, what they need to support is capabilities, and access and security primitives.…
> CSS only exists becuase javascript failed to develop a styling component to displace it
there is no sortage of projects that do it (especially during the react era, people wanted to get rid of both html and css) but they get pushed down by dogma/inertia mostly. There was iOS constraint layout language ported to js. Seemed pretty cool, but the guy behind it decided to give up and everyone was like welp we tried, didn't work.
Re: Show HN: X86CSS – An x86 CPU emulator written in CSS
#24Whoa! Completely unrelated but somehow unsurprising: Zero-day CSS: CVE-2026-2441 exists in the wild - https://news.ycombinator.com/item?id=47062748 - February 2026 (233 comments)
I don't think it's that unrelated. If you make a system way more complex than it should be (clearly the case with CSS) it's obvious the risk of vulnerabilities increases exponentially.
Re: Show HN: X86CSS – An x86 CPU emulator written in CSS
#25> Your browser is unable to run this demo. Please try with an up-to-date Chromium-based browser. Sorry to see internet regressing to Internet Explorer days. Edited to add: This is the message I get when using Firefox.
Not really, Internet Explorer was single platform and closed source.
Internet Explorer was certainly closed source, but it ran on many platforms.
It was popular on Mac Os (classic and X). It was also released for Solaris and HP-UX.
Re: Show HN: X86CSS – An x86 CPU emulator written in CSS
#26This is absolutely horrible... in a good way. Kinda like Doom in a PDF.
Well done.
Re: Show HN: X86CSS – An x86 CPU emulator written in CSS
#27Only Chrome ..
Re: Show HN: X86CSS – An x86 CPU emulator written in CSS
#28Earlier quoted context omitted.
[flagged]
Nice bait.
Go look at any web proposal. The Mozilla team consistently rejects proposals then relies on WebKit to piggyback on their decision.
This is what I mean by holding the web back. Don't even get me started with WebGPU still not being stabilized in Firefox, or the myriad of features WebKit has not implemented yet with respect to PWAs and service workers.
Really, the situation is more like "Chrome vs two modern IEs".
Re: Show HN: X86CSS – An x86 CPU emulator written in CSS
#29Earlier quoted context omitted.
Not really, Internet Explorer was single platform and closed source.
Internet Explorer was certainly closed source, but it ran on many platforms. It was popular on Mac Os (classic and X). It was also released for Solaris and HP-UX.
It was suffered on these platforms, because even IE for Mac didn't grant the 'compatibility' with 'web pages' designed for IE.
Re: Show HN: X86CSS – An x86 CPU emulator written in CSS
#30So is this x86 compatible, or 8086 compatible? Because those are different things