Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

lyra.horse

Post reply on HN
Print view View original

11–20 of 99 posts

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

#12

Post by StilesCrisis »

gurjeet wrote: post #11

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

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

#14

Post by notpushkin »

harsh-trvth wrote: post #13
gurjeet wrote: post #11

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

[flagged]

Nice bait.

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

#16

Post by notepad0x90 »

dmitrygr wrote: post #3

There 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. wasm hasn't displaced javascript, because afaik, the wasm spec for browsers doesn't require them to implement javascript (and ideally, CSS) via wasm.

Instead of distilling, simplifying and speccing CSS and Javascript, browsers caked on layers upon layers of complicated features. The idea that browsers should define and regulate the languages developers use to write front-end code needs to die.

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

#18

Post by Leszek »

notepad0x90 wrote: post #16
dmitrygr wrote: post #3

There 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.…

The complex parts of JavaScript are the semantics, not the syntax. You could reasonably easily spec a bytecode for JS to get rid of the syntax part, but nothing would change in the complexity (almost all modern engines parse to bytecode as the first step and operate on bytecode from then on).

If you wanted to implement JS in wasm, you'd either need a bunch of wasm extensions for JS semantics (dynamic object shape, prototypal inheritance, etc), or you'd need to implement them in wasm from scratch and basically ship a JS runtime written in wasm. Either that, or you need to change the language, which means de facto adding a new language since the old JS still has to stick around for old pages.

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

#20

Post by Dylan16807 »

> A hover-based clock, such as the one in Jane Ori's CPU Hack, is fast and stable, but requires you to hold your mouse on the screen, which some people claim does not count as turing complete for whatever reason, so I wanted this demo to be fully functional with zero user input.

That hover clock post is from 2023 and the "some people claim does not count" post is 2022. They were probably talking about the ones that make you check thousands of boxes to drive the logic forward.

Anyway, very cool advancement.

Post reply on HN