Although core memory is obsolete, computer memory is still sometimes called "core" even though it is made of semiconductors, particularly by people who had worked with machines having actual core memory. The files that result from saving the entire contents of memory to disk for inspection, which is nowadays commonly performed automatically when a major error occurs in a computer program, are still called "core dumps". Algorithms which work on more data than the main memory can fit are likewise called out-of-core algorithms. Algorithms which only work inside the main memory are sometimes called in-core algorithms.

To avoid clang-format formatting some portion of a file, you can do

The compiler can load uint16 c into a register and use the right ALU and branch ops on it, and JS_CCODE doesn't need other than jschar (uint16) for its macro-parameter.

Sloppy programmers should learn to be careful programmers instead of relying on a beautifier to make their code readable. Finally, since beautifiers are non-trivial programs that must parse the source, a sophisticated beautifier is not worth the benefits gained by such a program. Beautifiers are best for gross formatting of machine-generated code.

Getting the data

A key disadvantage of flash memory is that it can endure only a relatively small number of write cycles in a specific block.

Basically, flash generally is erased in blocks of ~64-512 kilobytes. Therefore, for every write anywhere within that block, the controller has to erase the entire block, using a write cycle for the entire block.

To be pedantic, FLASH memory is merely a form of EEPROM: There is a marketing / branding aspect here. Typically, the distinction used today is that EEPROMS are single-byte (or storage word) erasable / rewritable, while FLASH is block-based for erase/write operations.

Being at maximum temperature while running a workload isn't necessarily cause for concern. Intel processors constantly monitor their temperature and can very rapidly adjust their frequency and power consumption to prevent overheating and damage.

Since a local variable’s declaration always occurs before it is used, the VM can resolve them at compile time, even in a simple single-pass compiler. That will let us use a smarter representation for locals.