Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

"In no other era could a title like “Machine Code For Beginners” have been a children’s book."

This is so, so true. I cannot even imagine such a book for kids or even teenagers now. Something was lost when computers became powerful and boring.



...Really? I'm a teenager now. I'm actually learning z80 assembler. And GBZ80, which is actually closer to 8080.

I don't know if I'll ever manage it, but that's not because it's too hard, it's because I famously never finish projects.


Modern x86 assembly would probably fill a dozen thousand-page tomes...


Classic x86 (16 bit) not was hard to understand. The most problematic is the segmentation system. But beyond of it, it's very straightforward.

I got some knowledge from one of the Norton's book.


Well, yeah. Classic x86 was a well known instruction set. Not so for modern x86.

Segmentation still sucks, though.


...Which is why nobody actually knows x86. Yet another reason it sucks. Also the reason I'm not trying to write x86 code.

I mean, seriously Intel. Memory Segmentation? Yuck. And that's just the tip of the iceberg.


If you think x86 sucks (and I agree), how about learning ARM or MIPS or SPARC instead of Z80? Or if you want to stick with oldschool, maybe m68k.


Several reasons.

-Simplicity: The Z80's instruction set is dead simple, and thus easy to wrap your head around.

-Availability: Z80 chips are dirt cheap (and if you want to build a computer around it, designs are readily available).

-Ease: As a new assembler programmer, Z80 assembler is considerably more high level than, say, 6502 assembler.

-Other Factors: GBZ80 is hugely useful, especially to me, because I've got a Gameboy.

Some of those other architectures are on my list as well. Like m68k (and its cousin, the 6809): if only I could still buy the chips. 6502 isn't on your list, but it's on mine.

Also, ARMv4T, for the ARM7TDMI: GBA hacking could be fun.



What, what machine is this? Trillek?

oh my god, they're still working on it!

Well, this is very exciting.


Well, you could just make use of the ARM chip on your mobile phone and besides some boilerplate code to start your own Assembly code, do some ARM demos. :)

But yeah, GBA coding is also cool.


My phone runs Android. I shudder to think of the boilerplate involved.



Thanks! But it wasn't the prospect of the assembly that scared me: Android's Java API is a disgusting mess that I would happily never touch again for as long as I live.


Which is why even if it sounds foolish, I have more fun with UWP than Android.


I'd buy that. As much as I hate Microsoft, they have a much more fun ecosystem to work in than Android's (or so I've heard). C# isn't my favorite language, but there's less brain damage than there is in Java.


Not only C#, all the OS APIs are available to all languages including C++, not the half baked NDK experience and everything is compiled to native code on the store before downloading into the devices.

Not like the great idea from Google to do AOT on the device itself, which was so good that had to create an hybrid solution on Android N.


Oh. I didn't know that, and that sounds great. Or at least, way better than the NDK

I would gladly switch to a platform other than android for my smartphone, but as bad as Android is, everything else seems to suck more.


Reasonable enough. Good luck. I think your efforts will be rewarded.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: