From 5b31af58be0e9a94950eb025e6b31f77eb8c394a Mon Sep 17 00:00:00 2001 From: Miquel Sabaté Solà Date: Mon, 10 Feb 2025 10:06:42 +0100 Subject: Tune down my comments on non-assembly MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Miquel Sabaté Solà --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'README.md') 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. -- cgit v1.2.3