DYNA Fall 2025: 29-30 September. More info

The Dyalog Duck

Why do images of ducks appear here and there on this site and in our social media channels, and why do people regularly (and often anonymously!) send us rubber ducks for our collection?



The Quacking Tale of the Dyalog Duck!

In July 1989 we launched Dyalog for DOS/386, our first 32-bit version for DOS. As part of this product we supplied an auxiliary processor interface to the DOS/386 graphics library GSS*CGI. Pete Donnelly was asked to give a presentation on the new graphics capability. Undaunted, Pete bought the book Introduction to the Graphical Kernel System (GKS) . The first chapter included the co-ordinates for plotting a duck, and Pete used these to create a simple duck outline.

The very first Dyalog Duck as plotted by Pete Donnelly in July 1989.

These humble beginnings led to an graphical tutorial workspace that has graced nearly every version of Dyalog since 1990. Our anatine friend has morphed into various guises to demonstrate new functionality as Dyalog has evolved, from OLE and .NET ducks to bouncing ducks (to illustrate multi-threading) and polychromatic rotating bouncing ducks as graphical capabilities increased.

Before we knew it, the duck had established itself as the company’s emblem – we reached a point when people complained if there were no ducks! We even gave out little blue rubber ducks at our first user meeting (2003). Today, the duck tests are always one of the first tests performed on any new hardware.

A dyalog APL branded duck!


Jada Andrade

Send us a Duck!

Over the years, many people have sent us ducks to add to the collection in our Bramley office. Some donors we know, and some have remained mysteriously anonymous! If you would like to send us a duck, you can find our address here.

Jada, Administration Assistant

Get Support

Technical advice and assistance on all aspects of Dyalog usage is available by e-mail (support@dyalog.com) and/or telephone (+44 1256 830030 – limited to U.K. office hours). Limited advice on design and coding is available, but is not intended to replace the use of the printed and on-line documentation. Except when reporting an issue with the software, users are encouraged to seek advice from the user community via the Dyalog Forum (reading the content of the forums does not require membership).

Search our website...