_NetNomad

damn it seven, why did you have to eat nine?

since the kid presumably likes games and/or memes i would suggest starting with this beatle classic https://youtu.be/dJ1KaspORsE

>does good things for bad reasons  
>gluttony is considered by many to be bad

kirby. kirby is my favorite antihero

my first instinct is to recommend DEVO

people are recommending the retroid pocket 5, but i had a flip (1) which is internally equivalent to a 3+ and it ran gamecube perfectly. the flip was discontinued (and for good reason, it's battery had a nasty tendency to go spicy pillow) but you can buy the 4 new cheaper than the 5 and there are a few used 3+s floating around on ebay

interesting read. usually when people lay out the history of the series, they call 20 years ago the dark ages and 10 years ago as when things started to turn around. the thing for me is that 20 years ago we were still getting amazing side games that kept the lights on like the Advance series, and it was only when those stopped and Sonic Team had to stand on their own that things really fell apart. but now here we are with then collaborating with others and getting gold like Murder of Sonic the Hedgehog and Superstars, and meanwhile Sonic Frontiers is the first Sonic Team Sonic game i'd call genuinely good since... Adventure 2? Which speaking of which just got a brilliant movie adaptation. we're so back

that's the beauty of federation. when one planet goes down the rest stay up!

i'd love if they skipped ahead of TOS and did a show set in or after the movie era. bring on the monster maroons!

newly-confirmed fifth season will run for six episodes

remember when seasons were a season long

i think you're mixing up a few different things here. beam-racing was really only a thing with the 2600 and stopped once consoles had VRAM, which is essentially a frame-buffer. but even then many games would build the frame in a buffer in regular RAM and then copy everything into VRAM at the vblank. in other cases you had two frames in VRAM and would just swap between them with a pointer every other frams. if it took longer than one frame to build the image, you could write your interrupt handler to just skip every other or every three vblank interrupts, which is how a game like super hang-on on the megadrive runs at 15 FPS even though the VDP is chucking out 60 frames a second. you could also disable interrupts when the buffer was still being filled, which is how you end up with slowdown on certain games when too many objects were on the screen. too many objects could also lead to going over the limits of how many sprites you can have on a scanline, which is why things would vanish- bit that is it's own seperate issue. if you don't touch VRAM between interrupts then the image shown last frame will show this frame as well

transporter room, this is ensign crusher, requesting biological waste fluid transport from my station to matter recyclers, and a new pair of pants from my quarters to my legs

COBOL is still being updated because, believe it or not, people are still writing COBOL