I started up Vice the other day and had a fun time playing some of the old games I had reviewed with a 5 out of 5 score in the past. I played Star Post with my 7-year-old son sitting next to me, absolutely riveted as the game accelerated. Then we played Panther, Skramble, Space Worm, Air Traffic Controller. Captain Fizz Meets The Blaster Trons. Thought about some Force 7, but I get pretty freaked out by the music and tension even as an adult, so we gave it a pass. All really great games, some available on other platforms too. For the hardware side, be sure to check out the Retro Battlestations[0] subreddit.
I have a real C64 (along with a MSSIAH cartridge to make a nice synth), but rarely have the time or space to tinker with it.
He talked about how back in the early days ram and cpu was pretty much equal in clock. Thus if you could fit your program in ram, you could calculate how fast your program would run based on how many instructions you used to do things.
These days the cpu is many multiples fasters than ram, and thus cache misses is these days what disk access was back then. And because of how the cpu is now multiple cores, pipelines, and multiple tiers of cache, you can't simply sit down and step through the code to look for instruction bottle necks.
Never mind the layers upon layers of libs and whatsnot sitting between your program and the hardware.
Even games consoles are like this now, as they have turned into multimedia gateways. The last generation of consoles that came close was perhaps the PS2 and Gamecube (the Xbox was more a stripped down PC than a games console, and likely started the trend leading us to the present day).
Not "pretty much". On most early system they were clocked exactly the same. That includes things like the C64 and th Amiga, where there was no cache on the basic models (on Amiga models with 68020 or above there was some cache).
On the C64 in particular, timing things to the clock cycle was essential for some demo effects. E.g. if you used a hardware sprite, it'd "cost" the CPU access to RAM for two clock cycles per scanline that you had to account for if you wanted certain effects to work, for example.
That's exactly how I started programming, as a child, on a Z80 based system.
Oh man, don't say that! When I first got into C64 nostalgia, you had the older camp that was still staying productive on the 64, and us twenty-somethings nostalgic for the computer and games we grew up with.
Now we've got kids of our own, grey hairs and yellowed machines. At least my son got a kick out of playing Ultima V with me.
So, I say they look pretty old with acknowledgement that it means I'm getting up there, too. I don't mean to demean or dismiss the folks at that conference. It's totally my kinda scene, and I'm sure I'd have a great time talking to any one of them.
It's been a long time since I thought I'd see the day when Commodore conferences were getting bigger over time.
The crowd looks pretty old (not to say I'm young), and I think it's likely that this will be like classic cars. It'll come and go, as a phenomenon (or, at least, the era of what makes something "classic" will shift forward). But, it's fun while it lasts. I'd really like to make it to an 8 bit computer show one of these days.