4 ms·

I learned C on this compiler. Very fond memories

malux85 3y ago
Me too! On a bunch of old 486 machines my high school library threw in the trash (I fished them out after school) Frankensteined a few together until I had 4 machines, connected their serial ports, and learnt C and how to use a chess library to make them play chess against each other, it took me years but I leant heaps, Also got my first exposure to a decent graphical desktop, Desqview/X!
slim 3y ago
Fond memories of RHIDE. It was as capable as borland C
gpderetta 3y ago
I started with some 16bit Turbo C++ variant (I hardly remember), but quickly moved to DJGPP and protected mode (with Allegro). Great memories!
kunjanshah 3y ago
I learnt game programming with this and Allegro!
- busterarm 3y ago
  Gosh I remember trying to wrap my head around this and Allegro in my early teens. Specifically for use with Mugen. Years later I learned SDL/SDL2 and found them much much easier.
  - sgt 3y ago
    Same, Allegro was very impressive, and I built a little game in it. However, I remember I got stuck on something that I didn't quite fully understand at the time. Hell of a lot of fun though. Re SDL - exactly! Same path. It's been years since I wanted to play around making a game. I was thinking of building something in the love 2d framework now. What do you think of that?
  - deaddodo 3y ago
    That's funny, I always found allegro (4 or 5) easier than SDL. Allegro's performance had some issues for me, which is why I switched.
    - gpderetta 3y ago
      Agree, it is all fuzzy now, but I remember allegro docs being very good.
      - deaddodo 3y ago
        Yeah, that and it wasn't as low-level as SDL. You didn't have to manage your draw instance, textures, screen flipping, frame locking/time deltas etc. It was much more conducive to the paradigms of what a game loop actually looks like. But, for those same reasons, if you did something crazy (like I did with my first isomorphic engine), it could quickly get unmanageable with resource leaks. Nowadays, I just recommend raylib, if you want a more "game"-oriented (vs "graphics"-oriented) library. I just wish someone would expand the docs so it wasn't as difficult for new gamedevs to jump in.

Me too! On a bunch of old 486 machines my high school library threw in the trash (I fished them out after school) Frankensteined a few together until I had 4 machines, connected their serial ports, and learnt C and how to use a chess library to make them play chess against each other, it took me years but I leant heaps, Also got my first exposure to a decent graphical desktop, Desqview/X!

slim 3y ago

Fond memories of RHIDE. It was as capable as borland C

gpderetta 3y ago

I started with some 16bit Turbo C++ variant (I hardly remember), but quickly moved to DJGPP and protected mode (with Allegro). Great memories!

kunjanshah 3y ago

I learnt game programming with this and Allegro!

busterarm 3y ago
Gosh I remember trying to wrap my head around this and Allegro in my early teens. Specifically for use with Mugen. Years later I learned SDL/SDL2 and found them much much easier.
- sgt 3y ago
  Same, Allegro was very impressive, and I built a little game in it. However, I remember I got stuck on something that I didn't quite fully understand at the time. Hell of a lot of fun though. Re SDL - exactly! Same path. It's been years since I wanted to play around making a game. I was thinking of building something in the love 2d framework now. What do you think of that?
- deaddodo 3y ago
  That's funny, I always found allegro (4 or 5) easier than SDL. Allegro's performance had some issues for me, which is why I switched.
  - gpderetta 3y ago
    Agree, it is all fuzzy now, but I remember allegro docs being very good.
    - deaddodo 3y ago
      Yeah, that and it wasn't as low-level as SDL. You didn't have to manage your draw instance, textures, screen flipping, frame locking/time deltas etc. It was much more conducive to the paradigms of what a game loop actually looks like. But, for those same reasons, if you did something crazy (like I did with my first isomorphic engine), it could quickly get unmanageable with resource leaks. Nowadays, I just recommend raylib, if you want a more "game"-oriented (vs "graphics"-oriented) library. I just wish someone would expand the docs so it wasn't as difficult for new gamedevs to jump in.