About the service
I write and port programs in the Draco language for retro and modern systems. Draco is a systems language in the Pascal and Algol family from the Amiga and CP/M era, and I work in it live: clean procedures, tight work with records and pointers, low-level control—the very thing this language was created for. Do you have an old source tree that hasn't been built in ages, or a fresh idea for vintage hardware? I turn it into clean, working Draco code.
What you get: new programs from scratch in idiomatic Draco; porting old Draco sources between platforms; translating procedures from C, Pascal, or assembly into Draco; cross-compilation so the same logic runs on a real 68k or Z80 machine and on a modern host via emulator. I set up the toolchain, document the build steps, and deliver a repeatable process—not a one-off binary.
Typical tasks: revive a CP/M utility, rebuild an Amiga tool that lost its compiler, wrap an old library with a modern interface, or write a demo and hobbyist software for enthusiast machines. Every delivery comes with commented source, a build script, and notes on the quirks of the target platform so you or your team can maintain the code going forward.
I care about correctness on constrained hardware: fixed memory, no safety net, precise byte layout. Send me listings, disk images, or just a description of the goal—I'll honestly estimate the scope before we start.
What you get: new programs from scratch in idiomatic Draco; porting old Draco sources between platforms; translating procedures from C, Pascal, or assembly into Draco; cross-compilation so the same logic runs on a real 68k or Z80 machine and on a modern host via emulator. I set up the toolchain, document the build steps, and deliver a repeatable process—not a one-off binary.
Typical tasks: revive a CP/M utility, rebuild an Amiga tool that lost its compiler, wrap an old library with a modern interface, or write a demo and hobbyist software for enthusiast machines. Every delivery comes with commented source, a build script, and notes on the quirks of the target platform so you or your team can maintain the code going forward.
I care about correctness on constrained hardware: fixed memory, no safety net, precise byte layout. Send me listings, disk images, or just a description of the goal—I'll honestly estimate the scope before we start.