Live data from Hacker News

Show HN: X86CSS – An x86 CPU emulator written in CSS

lyra.horse

41–50 of 99 posts

Re: Show HN: X86CSS – An x86 CPU emulator written in CSS

#41

Earlier quoted context omitted.

Why is the 8086 not equivalent to x86? PCLMULHQHQDQ is from the CLMUL extension, which only began appearing in CPUs in the early 2010s - are CPUs from before then not x86?

x86 is an overarching group. Each processor is backwards compatible, I believe, so a 486 can run 8086 code, but they are not equivalent. If I download an x86 version of a program, I don't expect it to be written only in 8086 instructions

When you download an x86 program you're making a lot of other assumptions too, such as what the target operating system and hardware are. Even 8086 MSDOS software won't directly work in this emulator because it's not emulating DOS nor an IBM compatible, it has it's own addresses for the I/O. It's still x86 though.

Re: Show HN: X86CSS – An x86 CPU emulator written in CSS

#42
post #25

Earlier 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.

Internet Explorer on Mac was a completely different rendering engine (Tasman) to Windows (Trident). The only that was the same was the name.

(I swear at some point my brain will run out of space because it’s full of useless things like this.)

Re: Show HN: X86CSS – An x86 CPU emulator written in CSS

#43
post #4

I think we can look forward to running this on more non-Chrome browsers once @function [0] gets wider support? [0]: https://caniuse.com/wf-function

It relies on a few things, but @functions, if() statements, and container style queries are the main ones.

Some of those things are included in this year's interop

https://wpt.fyi/interop-2026

Re: Show HN: X86CSS – An x86 CPU emulator written in CSS

#44
post #21

I realy hope an AI did this intead of human, such a waste of time (the css part, not the x86)

Don't look at the end destination, look at the journey to the destination

* Learn low-level details of a basic but real-world CPU

* Practice the brain gymnastic of programming an atypical Turing-complete computer

Your created new connections in your brain, put to use some of the old established connections. Having a machine spit-out the emulator would rob you of all that. Like, you can drive from A to B, but running for A to B can do you much good.

Re: Show HN: X86CSS – An x86 CPU emulator written in CSS

#47

Incredible achievement. Horrible development on CSS front. CSS should NOT be becoming turing complete. Nor any other DSL.

> CSS should NOT be becoming turing complete. Nor any other DSL

Hasn't it been so for a while? I mean I agree with you but it's a bit late

Post reply on HN