we had no experiments to do, but a bunch of reading to follow up on.
i first started to look at let vs var, and got introduced to es6 standards; via daniel shiffman’s video. learnt about automatic hoisting before es6.
then went into translators. that rabbit hole led me to cpu-land.
The CPU always reads machine code directly from RAM, and code can’t be run if it isn’t loaded into RAM.
The CPU stores an instruction pointer which points to the location in RAM where it’s going to fetch the next instruction. After executing each instruction, the CPU moves the pointer and repeats. This is the fetch-execute cycle.
found bits and bytes tvo.
“the computer is not a calculator. it’s a logic machine”
a program is stored in the ram. the cpu understands how to process the instructions via the rom.
https://www.youtube.com/watch?v=Gq9OYkI5ju4
saw david rios’s predator screen, from when he was a student.
