It looks like they’re going for “machine code” being directly putting numbers in memory, but if you know what you’re doing that’s pretty much just assembly in an obscure op-code dialect.
Some middle-aged guy on the Internet. Seen a lot of it, occasionally regurgitating it, trying to be amusing and informative.
Lurked Digg until v4. Commented on Reddit (same username) until it went full Musk.
Was on kbin.social (dying/dead) and kbin.run (mysteriously vanished). Now here on fedia.io.
Really hoping he hasn’t brought the jinx with him.
Other Adjectives: Neurodivergent; Nerd; Broken; British; Ally; Leftish
It looks like they’re going for “machine code” being directly putting numbers in memory, but if you know what you’re doing that’s pretty much just assembly in an obscure op-code dialect.
You don’t know how to do something in raw JavaScript. You’re not even sure you should. You find a library / module / package / whatever-the-name-is-this-week on the Internet. You paste it into your code. Your code now works. Your code is now 1MB larger. This web app is heavy, man.
Wait until you learn that postfix conditionals are syntactic sugar and the compiler* turns that line into the equivalent of $debug and print(debug message)
, putting the conditional in first place, a lot like the ternary operator.
* Perl compiles to bytecode before running.
The ternary operator itself isn’t implemented in terms of and
(and or
) but it could be.
It’s the machine language monitor on the 40-column screen of the Commodore 128 (or, more likely, an emulator of the same). I had a whole part about that, BASIC
DATA
statements full of numbers, and about how anyone with any sense actually used an assembler even back then in an original draft of my comment, but decided to keep it brief.