4 ms·
Anecdotally, I recently went back and did some QuickBasic 4.5 programming, and was surprised how decent the experience actually was. I was on a retro kick, and
by 32bitkid 11y ago
Anecdotally, I recently went back and did some QuickBasic 4.5 programming, and was surprised how decent the experience actually was. I was on a retro kick, and was working backward/up to to doing some IBM PCjr hardware cartridge programming/ROM design. I still have a stack of old programming books from the mid 80's and early 90's and it was great to dust them off and re-read them with a fresh/older set of eyes.
I ended up doing some simple graphics programming on an old 386sx. Using QB for high-level code, and interfacting with some ASM for lower level graphics and data processing, it was actually quite pleasant.
But then, the reference PCjr that I was targeting/experimenting on finally gave up the ghost and died, and I lost interest in hunting down a new one... Poor little guy.
What I took away from the experience is while the tools were more primitive, it wasn't the languages that sucked when I was learning to program in the mid 80's and early 90's as a kid; it was me. I sucked at programming.
- vram22 11y ago>I was on a retro kick Retro programming can be great fun. I dive into it - a little - every now and then. E.g. Turbo Pascal 3, Turbo C 2, Icon, Forth, BASIC even. I think I still have a copy of Delphi 1 on CD - it came as a promo with a UK computer magazine I bought at a roadside newsstand. And used it to write some small apps. Surprisingly the apps worked even on much later versions of Windows than were current when Delphi 1 was released, though of course the widgets looked old-style. Also fun is exploring offbeat languages (that are not retro). Pike and ElastiC come to mind as ones I've checked out, and there are others.