aboutsummaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
Diffstat (limited to 'README.md')
-rw-r--r--README.md4
1 files changed, 3 insertions, 1 deletions
diff --git a/README.md b/README.md
index e17ac1f..d60f67f 100644
--- a/README.md
+++ b/README.md
@@ -34,7 +34,9 @@ performance critical bits in assembly and leave the business code in C so it's
easier to understand or debug. That certainly is a possibility, but in the end
the mixing of both languages can go wrong in different and hidden ways, makes
building and linking more complex, and, in my humble opinion, for not too much
-to gain. Hence, just stick with assembly and you should be fine.
+to gain. Or at least that's how I feel, and programming in C might just be fine
+for some people, but I prefer doing everything in assembly on NES/Famicom
+development.
That's why for the rest of this guide we will be talking about assembly and
never about C or any other languages.