I realy hope an AI did this intead of human, such a waste of time (the css part, not the x86)
If an AI can do this, it's definitely an AGI.
Show HN: X86CSS – An x86 CPU emulator written in CSS
51–60 of 99 posts
Re: Show HN: X86CSS – An x86 CPU emulator written in CSS
#52Incredible achievement. Horrible development on CSS front. CSS should NOT be becoming turing complete. Nor any other DSL.
That is the problem though, DSLs always end up becoming turing complete, because there is always that use case they don't cover.
Re: Show HN: X86CSS – An x86 CPU emulator written in CSS
#53Next step: Start Chrome in emulated X86CSS and start X86CSS in emulated Chrome.
Re: Show HN: X86CSS – An x86 CPU emulator written in CSS
#54I have mixed feelings. On the one hand, it's impressive, but on the other, it's concerning that CSS is turning into "JavaScript 2".
Re: Show HN: X86CSS – An x86 CPU emulator written in CSS
#55The moxy of this is inspiring.
I'm curious to know what you would rate as the most important features to make this work? It seems like calc+if do a lot of the heavy lifting, but the new function syntax is what makes instruction lookup tractable.
Re: Show HN: X86CSS – An x86 CPU emulator written in CSS
#56Definitely in the "they didn't stop to think if they should" category.
Re: Show HN: X86CSS – An x86 CPU emulator written in CSS
#57Earlier quoted context omitted.
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".
There’s nothing new to discuss here really. You know the counterarguments to your position better than I do.
Re: Show HN: X86CSS – An x86 CPU emulator written in CSS
#58Definitely in the "they didn't stop to think if they should" category.
They probably did, and just determined that it would be fun.
The other week I had a fun project to implement IPv6 support in TempleOS. I did stop to think whether I should, and determined that absolutely not.
I asked Claude to start planning on doing it. It started referencing ZealOS, which is a fork of TempleOS and already has a functioning TCP stack.
That's when I determined that it would no longer even be fun, because someone else had already done all the heavy lifting, and gave up.
Re: Show HN: X86CSS – An x86 CPU emulator written in CSS
#59I have mixed feelings. On the one hand, it's impressive, but on the other, it's concerning that CSS is turning into "JavaScript 2".
Now we can embed a cryptominer on a page even with JS disabled! /s
Re: Show HN: X86CSS – An x86 CPU emulator written in CSS
#60Very cool. The horsle demo made me think, how hard would it be to add a virtual memory address (or a non-8086 RAND instruction) that returns a random byte (that would allow it to pick a random value and get a standard wordle working in principle)
I see CSS random() is only supported by Safari, I wonder if there's some side channel that would work in Chrome specifically? (I guess timing the user input would work)