Tips? Suggestions?

[Menne31]

Hey guys! I'm new the the forums and just wanted to kind of introduce myself and ask for some advice from some of the members about programming. I'm a junior in college going for CIS (computer information systems) but I really enjoy some creative coding outside of databases also. I figured programming for the atari would help me combine two of my favorite things Retro gaming and programming! Ok to the point I'm just looking for some suggestions on where to start. I've been reading the programming for newbies sticky and I've read a lot about bB. Is there anyone here that is kind of in my situation that maybe wants to try learning together (I have a hard time keeping on task if not pushed by someone else). I have a few RL friends that are interested, but I think they will probably call it quits pretty quick. Is it easier to start learning with bB or is going the assembly language route better? If I'm going to learn I really want to start the right way because I know it can make a big difference in the long run. Is using bB just as powerful as using straight assembly?

 

Any tips, suggestions, or links are highly appreciated.

 

Also if any senior programmer responds do would you mind if I pm you if I have some questions. Thanks for the help guys!

[tokumaru]

Is using bB just as powerful as using straight assembly?

No, it's not. The 2600 has a very rudimentary video system, so in order to show anything meaningful, games have to rely on "kernels". Since the amount of processing available is very limited, kernels have to be carefully tailored for each game in order to make full use of the hardware. AFAIK, bB has a handful of general-purpose kernels, so it obviously can't make the best use of the hardware for every possible game.

 

Also if any senior programmer responds do would you mind if I pm you if I have some questions.

I'm not a senior programmer when it comes o Atari (I guess I can say that about the NES though), but I can say that the forums are better for asking questions, because others might learn from the conversations as well. PM's are kinda selfish, because only you get to learn. Don't you agree?

[Menne31]

Is using bB just as powerful as using straight assembly?

No, it's not. The 2600 has a very rudimentary video system, so in order to show anything meaningful, games have to rely on "kernels". Since the amount of processing available is very limited, kernels have to be carefully tailored for each game in order to make full use of the hardware. AFAIK, bB has a handful of general-purpose kernels, so it obviously can't make the best use of the hardware for every possible game.

 

Also if any senior programmer responds do would you mind if I pm you if I have some questions.

I'm not a senior programmer when it comes o Atari (I guess I can say that about the NES though), but I can say that the forums are better for asking questions, because others might learn from the conversations as well. PM's are kinda selfish, because only you get to learn. Don't you agree?

 

Thanks for the input and yes I definitely do agree that it would be selfish to keep it to pms. I will keep posting on the forums thanks again =]

[RevEng]

AFAIK, bB has a handful of general-purpose kernels, so it obviously can't make the best use of the hardware for every possible game.

It's true enough that bB has a handful of general-purpose kernels, but it should be noted that it doesn't limit you to them. bB allows you to use inline assembly and add your own kernels.

 

Personally I use bB with the mix-and-match approach, using pure bB when a high level approach will save me dev time (more time for features and polish) and switching to assembly when low level control is beneficial.

 

See the 21 Blue link in my sig for one game that benefited from the mixed approach.