11 March 2016 - Forum Rules
Started by fairdenizen, October 21, 2013, 10:28:09 PM
Quote from: Bregalad on November 06, 2013, 08:32:38 AMNo I wasn't kidding, and I was just saying ASM is easier to understand - I said it was harder to work with, which is basically what you're saying, so we both agree. I never said ASM was elegant, either.
QuoteOverloading - can be your "fault" (using your own term), but it might more likely be the "fault" of the library you're using because either 1) everyone uses this library and 2) this is the standard way of doing it and your language doesn't offer any alternatives.
QuoteJust ask a random OOP programmer how complex is string concatenation with "+". Nobody even thinks that this will allocate memory for a new String object concatenating both strings and so on, unless explicitly asked.
QuoteI think our agreement comes from the definition of what is "understood":
QuoteYou're telling me that an algorithm written in high level is easier to understand, which is true, and I'm telling you individual instructions in ASM are easier to understand.
QuoteEDIT : I saw you mentionned MIPS, and I'd say that it's a great exemple : MIPS instructions are even simpler than say 6502 instructions, as there is no status flags, multiple adressing modes or register non-orthogonality, so this makes MIPS instructions simpler to understand. However, a MIPS assembly program would be even harder to understand, because more instructions should be used in a more tricky way to get the work done.
QuoteBasically programming is a trade-off between simplicity of the individual instructions, and simplicity of the whole programs. Assembly goes for the former, high level OOP for the later.
Quote from: Bregalad on November 06, 2013, 12:52:23 PMDelays slots are a terrible idea. Whoever had the idea to introduce them was seriously retarded.
Quote from: Bregalad on November 06, 2013, 12:52:23 PMFor example I'd consider someone who tends to create lots of new instances of objects a bad programmer (even if perhaps myself would do this, because I don't care when I use HLL).
Quote from: tankendog on November 10, 2013, 06:55:16 PMThis is the hardest 2 things. As asm is simple its using it in conjunction with the hardware to program. Resources are there, but none are going to allow you to sit down and code mario from scratch. Most resources were fan made. Most are outdated, and terminology is hit/miss. And figuring things out can be extremely frustraiting. I still cant figure out how to scroll horizontally/view tiles I store into vram. And OAM is insanely hard to understand by the limited documentation, I had to scrap 3-4 weeks worth of effort because it is almost impossible to debug the code. I am glad I got a chance to experience this, but it would be even easier to write pseudo-snes style game engine than to program in the SNES language itself.
QuoteOff topic a bit, But does someone know how to scroll the screen to the right and left? if someone could PM me, Id make babies with you. <3
Quote from: tankendog on November 10, 2013, 06:55:16 PM And OAM is insanely hard to understand by the limited documentation, I had to scrap 3-4 weeks worth of effort because it is almost impossible to debug the code.
Page created in 0.075 seconds with 20 queries.