From 9c1dae2099f257d5b49601f27a80fe2559d21785 Mon Sep 17 00:00:00 2001 From: Miquel Sabaté Solà Date: Mon, 10 Feb 2025 14:09:58 +0100 Subject: Remove the "easy to debug" when talking about C MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Miquel Sabaté Solà --- README.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index 47f6a91..80d9274 100644 --- a/README.md +++ b/README.md @@ -31,12 +31,12 @@ most learning resources are also given in assembly. That being said, one good argument could be made that you could write the most 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, linking and debugging more complex, and, in my humble opinion, for not -too much 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. +easier to understand. That certainly is a possibility but in the end the mixing +of both languages can go wrong in different and subtle ways, makes building, +linking and debugging more complex, and, in my humble opinion, for not too much +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