Introduction...

...to Wabbitware.

Wabbitware is derived from the term ‘wabbit’ which is used in hacker jargon to describe a certain class of software which self-replicates or which induces infinite self-replication but is not a worm or virus.

The manifestation of this first Wabbitware project will be a precompiled, closed-source software piece which, when executed will spawn a copy of its own source code onto the host machine. Rather than using a copyleft legal framework to allow or enable the modification and redistribution of software, Wabbitware forces its source code onto the host machine. It will also preform the secondary function of (pre)compiling any modifications or additions to the source code into a format which ensures that these mutations will be transferred to the next version (generation) of Wabbitware.

Once the first version of Wabbitware is released it will be programmed to always ensure its own propagation and genealogy. It contradicts the proprietary model of software production which produces the feature saturated, version frenzied and bounded software, in exchange for open collaborative practices and limitless potential for creativity and individuation.


If you would like to contribute to this project but do not have any coding experience please read the Contribution section of this article about Wabbitware.

General information about Wabbitware.