Yeah, I’m not a model for good programing. I don’t program professionally, I just like challenging myself in my hobby projects.

No, I don’t do anything professionally. I just enjoy challenging myself.

I am both the left guy and right guy. If you can’t program without using a memory safe language, it’s a skill issue. But I also don’t want to switch to rust because I like the challenge of manual memory management. (Also rust’s syntax and semantics looks like it was designed by a monkey attacking a typewriter.)

Rust is already obsolete, compared to Stingpie’s excellent assembly language, paired with object oriented programming!

This is the SEALPOOP specification:

1. an assembler must create a binary program which satisfies the programmer’s specifications.
2. a compiler must translate the programmer’s code into SEALPOOP’s parallel instruction set source, which should be fed into the SEALPOOP PISS assembler.

What do you mean by offensive?

Did you guys find this hard? There are only four possible ways to move a ring, two of which are disallowed by the rules. Out of the remaining two, one of them is simply undoing what you just did.

There are actually two standards here. Kibibytes was introduced later as a way to reduce confusion cause by the uninitiated thinking the JEDEC standard refered to powers of ten instead of two. That’s why I’m saying that 64 kilobytes is equal to 2^16 bytes, because that’s what the original standard was.

I still use mb and kb as 1024 instead of 1000, because I prefer to not have units switched around from under me. 2^16 will always address 64kb, not 65.