aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorhachem <im@hachem.wtf>2026-09-07 09:16:38 +0200
committerhachem <im@hachem.wtf>2026-09-07 09:16:38 +0200
commit00cc575e74a2bdfbd313f6b5c525d458db716761 (patch)
tree43cca5f4f34cdf2bcef7c5d2ad58ed2d054d9411
parent9283b46a08a1c58c321b6c7ebad1353725c3bc47 (diff)
docs: update README
-rw-r--r--README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/README.md b/README.md
index 7c3847c..53e0579 100644
--- a/README.md
+++ b/README.md
@@ -1,5 +1,5 @@
# hdass
-hachem's dumb assembly super-set, pronounced "HD Ass".
+hachem's dumb assembly super-set, pronounced "HD Ass", or "headass"...depends on how you feel that day.
The entire point of this project is to provide a middle ground between C and assembly. If we think about why we still write assembly today, it's usually because we need direct control over what the CPU is doing. We want control over the exact instructions being executed, the memory, the stack and everything else that higher-level programming languages normally abstract away. The thing is, not every program written in assembly actually needs that control. Sometimes you want to write something close to the machine without having to manuall deal with every tiny detail yourself. You still want registers, explicit control over memory and a good understanding of what your program is doing, but you don't necessarily need to manually express everything as individual assembly instructions.