sack wrote:what oktup said on the software front - but don't get too hung up about learning assembler. after all - commodore basic 2.0 is so utterly shite it's pretty much got the usability of assembler with the speed of basic. It's not so much of a jump as you might think.
Yes. Microsoft originally wrote the C64's OS and BASIC, didn't they? Which goes a long way to explaining many things about the general shite-ness of it all - and adds a little irony, in that so many folks who are now Linux kernel hackers probably got into low-level coding, thanks to Microsoft.
I also think this is why Microsoft later got obsessed with sticking "Microsoft" in front of everything - Microsoft Windows, Microsoft Word, etc. - because they actually wrote a lot of BASIC interpreters and software for various computers that actually goes uncredited. By wedging the company name as officially part of the software's title, you force folks to give you credit and a free advert - which, fair play, is actually quite an amusingly clever strategy.
Anyway, yes, the difference between the C64's BASIC and using assembler is worryingly minimal in too many places. Pretty nearly everything dealing with hardware ends up being all PEEKs and POKEs to memory mapped registers - identical in usage to what you'd do in assembly code, but just slower. No "CLS", no "PRINT AT" or anything of that nature - half the keywords of other BASICs just ain't there.
So the BASIC offers you very little and then, simply, you've got a slow CPU (even the Spectrum was clocked at 2MHz, but the C64 is half that - the advanced peripheral chips like the SID and VIC did an awful lot of work in raising the C64, as, even at the time, the CPU was not too stellar or impressive by any means). And without kicking out the KERNAL (gotta love that Commodore spelling mistake, eh?) and BASIC, half the 64KB memory is gone. Hard enough getting a decent game to fit into 64KB, let alone half that.
Everything pretty much conspires to force you towards using assembly for all but the most basic (pardon the pun) of programs.
We've come a very long way since and it's perhaps a bit too easy to forget just how far we're talking. This thing is several thousandfold less than your typical modern PC in pretty much every department (mind you, it's also a testament to how much programming standards have fallen too - thanks to ever-increasing hardware allowing us to be, well, more "lazy" about things and say previously inconceivable things like "fuck optimisation" so casually and, more over, that such a statement is genuine economic reality, not just a way of dodging the bullet to avoid doing hard work - that what you see running on a C64 doesn't "look and feel" several thousandfold worse, all things considered).
But, at the same time, it's from a much simpler age. Technically, there are only "officially" 56 instructions, almost no registers (and, as memory runs about as fast as the CPU, this doesn't really matter much), etc. - so, yes, it's assembly, but it's as unintimidating as assembly is ever going to get.
So, I concur, the C64 BASIC is so shite, you gain effectively no advantage from using it. Your code ends up being a mess of PEEKs and POKEs and GOTOs everywhere - might as well go straight to using loads and stores and unconditional branches, as the BASIC programs end up really being perilously close to "assembly using a high-level syntax and line numbers".
Thus, gaining no real advantage from BASIC, just a series of disadvantages (and some nasty ones like having half the RAM eaten up and everything running slow as buggery on a CPU that ain't exactly the speediest in the first place), then, sorry, "resistance is futile" - bite the bullet and fire up the assembler.

"Words ought to be a little wild - for they are assaults of thought on the unthinking."
- John Maynard Keynes