rebane2001

this reads like slop

No, the API will not return the admin-only removal reason. The code path that causes this is in the post.

wait what the heck yeah, this is the same post as from a few days ago, i guess the comment and post timestamps got glitched??

(author of x86css)

Not possible, but it would be possible to reimplement Quake's logic and controls in CSS to have it run without JS. I was considering doing that for my next CSS crime project, though now that CSSQuake has hit the hn frontpage there is little point in doing so.

You cannot close HTML tags that way anyways, <br> and <br/> are the same, as are <div> and <div/>. The spec defines whether an element self-closes, the slash is just ignored.

(author of x86css)

not only do i think doom in css is possible, but both me and another css person were also planning on actually making it into reality

but it sort of feels demotivating to see js-powered css projects like this hit the frontpage, because if we do eventually make a css-only doom people will think its a repost or nothing special

edit: and to be clear, that demotivation is more of a problem of how the internet, virality, and news cycles work. the actual project here is still pretty cool!

the difference is that knowing 2^8 is generally not useful to people who don't know it

this here is something that's pretty useful to most ssh users, yet seldom spoken of

a better analogy would be comparing it to calling a very good, but not well-known restaurant a secret place - using the word to mean a hidden gem rather than an intentionally hidden secret

tldr is so good, i wish it was a part of the os the same way manpages are just to help out newcomers

it's a placeholder that gets replaces by the python script on build

Yes, CSS binary data transfer is possible in bith directions.

clock != looping, those examples already loop (dont need a line per iteration), but just dont have a built-in clock

and requiring a clock is imo dismissable, because pretty much all modern technology needs a clock too (either from the power grid, or from a hardware component designed for it)

I think x86 is still good because it's easily understandable. If I say it's an 8086 emulator, people who aren't familiar with the 8086 aren't gonna go "oh so like an older version of the same x86 on my computer". And "Show HN: CSS program that emulates a CPU that's a member of the x86 family" doesn't roll off the tongue.

I don't think calling it x86 is misleading, and this is coming from the perspective of someone who dabbles in rev and pwn of x86.

It's really easy, I was considering adding it.

The easiest way is to make an @property that's animated at ridiculous speeds that can be sampled to get (sort of) random bits.

I did not use any AI