Dio wrote:KlaxonCow wrote:And compared to "colour clash" monochrome character graphics and tinny little beep noises on the Spectrum, it might have had more "oomph" in its engine, but what could you really use it for, when the methods of output were so limited?
See the aforementioned comment on Elite

. The C64 has other compromises instead of course - the horrible 160-wide resolution in multicolour modes probably being the worst, and of course because of the speed of the CPU it could only update around half as much of the display per frame. And, of course, it was twice as expensive.
what I'm really saying is that it's a pain in the arse that Commodore didn't have the 3.5andabitMHz CPU instead, as it could have been exploited to good cosmetic effect, thanks to all the raster tricks you could play with the VIC-II.
Well, it could have used a 2MHz 6502 like the BBC, but I suspect the reason was penny-pinching on the CPU and custom chips - they would both have had to be specced twice as fast (the BBC had to use an odd technique in which the CPU dynamically downclocked whenever it hit a custom chip).
Yes, I agree on all points.
Of course, the reason why it was the way it was, is because of the economics, as you mention, and Tramiel wanting to do the whole "cheap computing for the masses" thing - which, in the long run, was absolutely the right thing to do, in "for the benefit of the human race" terms - as upping the clock on the CPU would have meant upping the clock on everything else (or implementing some elaborate scheme to handle having the various components running at different speeds - as with the BBC's "downclocking" thing). All of which would just have inflated the price - possibly by a little too much that it falls outside the price range of the "target consumer" and you lose the market and all the rest of it.
I understand why. But it's just a programmer's lament to moan about the technical compromises. The "if only" considering how much better the graphics would have been if Commodore has chosen simply to use double the RAM in multicolour mode instead. Or, talking about playing samples, as we were, imagine if the SID had had 3 independent volume controls for each voice, instead of one overall volume control.
As a low-level programmer who likes to bend the metal, I'd have much preferred - from a technical perspective - a fast CPU and exposed hardware. You know, the Archimedes principle - "give me a place to stand, and I will move the Earth".
Sometimes, I'm actually pissed off with the hardware guys because they try to make this all singing and all dancing chip which has "helpers" here and clever built-in functions there. Fuck that - give me shitloads of fast Turing machines and I'll work out how to get them singing and dancing to the right tune.
Perhaps I was the only one but I was kind of annoyed by 3D graphics cards initially - dubbing them "Quake accelerators" - because they were just too "fire and forget" for my tastes (and calling them "3D accelerators" when they only accelerated textured mapped polygons but not voxels, not raytracing, etc. was a misnomer I didn't like much either - again, I understand that it's just "marketing" and none of this means I wouldn't make full use of them, but, still, it's technically a misnomer as far as I'm concerned).
I'm now warming back up to them since "shaders" were introduced and the buggers have become properly programmable. Although, I still would prefer it, if they were just an exposed array of coprocessors, with some nice built-in matrix and trigonometric instructions. Because then they could be equally useful to accelerate ray-tracing and voxels and other types of 3D. Heck, you could even "abuse" them and exploit their processing power for things besides graphics. I mean, in a sense, isn't it a bit stupidly wasteful to have hardware with such immense processing power sitting around doing much of nothing most of the time, just waiting for you to run a computer game?
Again, I do appreciate all the economic reasons that lay behind these things. But, to a programmer, the thought of shitloads of processing power just sitting there doing much of nothing most of the time - well, it's like dropping Casanova into "the harem of a thousand willing beauties" and then telling him "don't touch!". WTF?!? You have got to be kidding me!
The C64 was the machine that proves it.
You're not supposed to be able to play samples at all. Nor should you be able to have more than 8 sprites on-screen at once. Nor should it be capable of displaying more than so many colours in certain graphics modes. Commodore hardware is still unique in allowing the ability to actually display different graphics modes on the same screen simultaneously.
There are C64 demos which regularly feature the supposedly impossible. Such as bump mapping. On an 8-bit. And folks still keep trying to push it further all the time, nearly two decades after the damn thing should have died.
All made possible because the VIC's internals were exposed and a programmer could reach into it with the CPU and mess around with it. Because Commodore were very programmer-friendly, making much effort to supply manuals that taught programming and exposed nearly every nitty-gritty detail about the machine you could think of. And, you know, has any machine been "hacked" far beyond its stated "on paper" capabilities than the C64 has been?
Actually, as I write this, I just hit "preview" and can see Istar's comment about "controlling the electron gun". Yes, that's exactly it. Give me a superfast CPU and then access to the electron gun and access to the speaker cone. The less bullshit in the way, the better!

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