When R Stopped Meaning RISC
From hand-typed hex on a Samsung SPC-1000 to ARM assembly on an embedded Linux board — the long, slightly anticlimactic story of RISC vs CISC. A look back — long before any of the tools we argue about now. Reaching for machine code The first machine code I remember was a handful of game routines for the Samsung SPC-1000, copied out of a computer-study magazine. Long strings of hexadecimal,…
In the early days of computing, machine code was written by hand using hexadecimal numbers, often copied from magazines or programmed directly into a computer. The Samsung SPC-1000 was one such device, and its hexadecimal code was etched into the minds of young programmers like the author. Moving on to Microsoft Macro Assembler (MASM), the author experienced the complexity of assembly language, which was a step beyond understanding the more straightforward computer instructions.
The RISC vs CISC debate emerged during this period, with RISC (Reduced Instruction Set Computing) machines promising better performance through simpler, more efficient instructions. The author's memory of this era is tinged with nostalgia and pride, as moments of accomplishment, such as implementing a compiler with a switch statement, were cherished.
The author eventually became immersed in the world of ARM architecture, a RISC-based processor, while working on embedded Linux systems. Though the battle between RISC and CISC ultimately fizzled, the author reflects on the journey and the lessons learned, appreciating the effort that went into acquiring this knowledge.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
