Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Kimmax1173072dQbasic is still a thing? 😂
bioDan540872dMy first programming language *sniff*
Fast-Nop2249971dThe reason you work with a shadow frame buffer is that it is switched to the actual screen right when the monitor syncs vertically. Makes only sense for CRT, but these were common back then.
If you fuck around with the active screen buffer right away, then depending on where the CRT ray is in relation to your poking, you may get an odd mix between the new picture and the old one so that moving things would seem to stutter.
Demolishun450271dYou could also dig up Turbo C++ for DOS. It has really good help files built in.
Parzi680471d@Fast-Nop not a shadow buffer in raw RAM, a DATA array.
The slowest shit in the world.
That's what these people use.
The PEEK/POKE method is around 4x faster, and MS-DOS only updates the screen data every frame even after I write to it ahead of the beam, so even on a CRT it looks okay.