z80 or C

I loved that game.

Use a C compiler for the Z80. Here's one;
http://www.bdsoft.com/resources/bdsc.html

Chances are that outside of this game, you won't be using Z80 again. If you find performance issues, rewrite parts of the code in ASM.

>>61517939
If you can't sort yourself out with action battle systems in game making programs then you're going to have motivation issues learning asm.

Prototype the game you want to make with something like love2d and then move onto C->z80. You may think it's a waste of time but you'll learn a lot about coding from making even the shittiest games. If you're doing this to learn shit don't be worried about stealing sprites either, just rip all the link's awakening sprites so you have placeholders.

>>61517939
z80 is a cpu, not a programming language. you could learn z80's assembly language but it would be a slow procces, i think you should program the z80 with c, that way you actuly know something useful at the end

>>61518459
>>61518763
I don't think asm is hard to learn, it is really logical which is great. Compilers are good but some shit is better done yourself since low power cpus like the z80 or microcontrollers can suffer a lot with bad conversions. I don't think it would take years, maybe a month or two if it's your main project.

There are some good YouTube videos about gameboy programming too.

>program z80 with C
Probably the best way to go since asm is specific and non transferrable. Still is a good idea to have some understanding, it definitely changes your perspective on good/efficient programming.

>>61517939
both c and z80 assembly are crap to learn programming

>>61519675

C is great as a first programming language. Z80 on the other hand... probably not a good idea. In fact, I'd think it would be kind of silly to want to program gameboy games these days. Aside from it being a dead platform, it's an annoying one too. You have to constantly switch around which "bank" of the ROM is in memory at any given time. You have 64K of address space, but many games can go as high as 1 or 2 MB. Beyond this, only half of this can be used to store data from the ROM. The rest is either working memory or used for I/O. The first 16K of code is fixed in memory, so you can only swap out a single 16K block of memory with another 16K block of memory, and all of the code associated with doing that swapping is basically going to have to be in that first 16K block of memory.

It's ugly shit and you shouldn't do it unless you're really looking for a challenge. Not something a beginner should do.

>>61520094
>C is great as a first programming language.
no. it's not abstraced enough from the underlaying machine, has missed +50 of plt, is the one of the shittiest PL at doing abstraction. someone who learned c missed a lot of fundamental concepts of programming (lambda expressions for example)

>>61520120
we've reached /g/ meme full circle. thread's done, everyone out.