Difference between revisions of "Main Page"

From SizeCoding
Jump to: navigation, search
(Welcome to SizeCoding.org!)
 
(12 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 
== Welcome to SizeCoding.org! ==
 
== Welcome to SizeCoding.org! ==
  
'''SizeCoding.org is a wiki dedicated to the art of creating very tiny programs for the 80x86 family of CPUs.'''  By "very tiny programs", we mean programs that are '''256 bytes or less in size''', typically created by members of the [https://en.wikipedia.org/wiki/Demoscene demoscene] as a show of programming skill.  The size of these tiny programs is measured by their total size in opcode bytes, and are usually presented as executable .COM files to be run in pure DOS, a DOS VM running inside another operating system, or an emulator that can run DOS such as DOSBox.   
+
'''SizeCoding.org is a wiki dedicated to the art of creating very tiny programs for most popular types of CPUs. As sizecoding is also popular on other hardware we recently opened the website for other plaforms as well, check the links below.'''   
 +
 
 +
By "very tiny programs", we mean programs that are '''256 bytes or less in size''', typically created by members of the [https://en.wikipedia.org/wiki/Demoscene demoscene] as a show of programming skill.  The size of these tiny programs is measured by their total size in opcode bytes, and are usually presented as executable .COM files to be run in pure DOS, a DOS VM running inside another operating system, or an emulator that can run DOS such as DOSBox.   
  
 
'''Despite their tiny size, these programs are able to produce amazing graphical displays, playable games, and sometimes music.'''  There are even some surprisingly effective programs in under '''16 bytes''', such as [https://trixter.oldskool.org/2012/12/17/maze-generation-in-thirteen-bytes/ a maze generator in 10 bytes], a [[Paint16b|mouse-driven paint program in 16 bytes]], and an [[M8trix_8b|"Enter the Matrix" screensaver]] in only 8 bytes.  
 
'''Despite their tiny size, these programs are able to produce amazing graphical displays, playable games, and sometimes music.'''  There are even some surprisingly effective programs in under '''16 bytes''', such as [https://trixter.oldskool.org/2012/12/17/maze-generation-in-thirteen-bytes/ a maze generator in 10 bytes], a [[Paint16b|mouse-driven paint program in 16 bytes]], and an [[M8trix_8b|"Enter the Matrix" screensaver]] in only 8 bytes.  
Line 7: Line 9:
 
'''The intent of this wiki is to teach x86 assembler programmers the various techniques used to create tiny demoscene intros.'''  While these techniques can be used for other applications (boot sectors, BIOS and firmware code, etc.), the information presented here is firmly oriented towards the demoscene.  Practicality and common sense are sometimes thrown out the window just to shave a single byte -- consider yourself warned.
 
'''The intent of this wiki is to teach x86 assembler programmers the various techniques used to create tiny demoscene intros.'''  While these techniques can be used for other applications (boot sectors, BIOS and firmware code, etc.), the information presented here is firmly oriented towards the demoscene.  Practicality and common sense are sometimes thrown out the window just to shave a single byte -- consider yourself warned.
  
This wiki is divided into the following major sections:
+
This wiki is divided into the following major sections for x86:
 +
 
 +
*'''[[Getting Started]]''' - What do you need to know before starting your first tinyprog?
 +
 
 +
*'''[[Techniques|Tips, Tricks, and Techniques]]''' - The meat of the wiki.  Lists of small opcodes, default environment settings, size optimization basics, and a ton of random tips.
 +
 
 +
*'''[[Case Studies]]''' - Analysis of existing award-winning tiny programs, with comments on what choices were made and why.
 +
 
 +
*'''[[Resources|Additional Resources]]''' - Discussion threads, competitions, repositories, and other external references that can aid you in your quest.
 +
 
 +
For other platforms check out the sections here:
  
:[[Getting Started]] - What do you need to know before starting your first tinyprog?
+
*'''[[RISC OS on ARM based CPUs]]''' - Create your tiny intro on ARM hardware on Risc OS.
:[[Techniques|Tips, Tricks, and Techniques]] - The meat of the wiki.  Lists of small opcodes, default environment settings, size optimization basics, and a ton of random tips.
+
*'''[[Motorola 68k based CPUS]]''' - Start Sizecoding on your Atari ST or Amiga.
:[[Case Studies]] - Analysis of existing award-winning tiny programs, with comments on what choices were made and why.
+
*'''[[6502 based CPUs]]''' - Commodore 64, Atari XE/XL, Atari Lynx, etc.
:[[Resources|Additional Resources]] - Discussion threads, competitions, repositories, and other external references that can aid you in your quest.
+
*'''[[Z80 based CPUs]]''' - For all your ZX Spectrum, Amstrad CPC, etc. sizecoding needs

Latest revision as of 15:58, 13 July 2020

Welcome to SizeCoding.org!

SizeCoding.org is a wiki dedicated to the art of creating very tiny programs for most popular types of CPUs. As sizecoding is also popular on other hardware we recently opened the website for other plaforms as well, check the links below.

By "very tiny programs", we mean programs that are 256 bytes or less in size, typically created by members of the demoscene as a show of programming skill. The size of these tiny programs is measured by their total size in opcode bytes, and are usually presented as executable .COM files to be run in pure DOS, a DOS VM running inside another operating system, or an emulator that can run DOS such as DOSBox.

Despite their tiny size, these programs are able to produce amazing graphical displays, playable games, and sometimes music. There are even some surprisingly effective programs in under 16 bytes, such as a maze generator in 10 bytes, a mouse-driven paint program in 16 bytes, and an "Enter the Matrix" screensaver in only 8 bytes.

The intent of this wiki is to teach x86 assembler programmers the various techniques used to create tiny demoscene intros. While these techniques can be used for other applications (boot sectors, BIOS and firmware code, etc.), the information presented here is firmly oriented towards the demoscene. Practicality and common sense are sometimes thrown out the window just to shave a single byte -- consider yourself warned.

This wiki is divided into the following major sections for x86:

  • Getting Started - What do you need to know before starting your first tinyprog?
  • Tips, Tricks, and Techniques - The meat of the wiki. Lists of small opcodes, default environment settings, size optimization basics, and a ton of random tips.
  • Case Studies - Analysis of existing award-winning tiny programs, with comments on what choices were made and why.
  • Additional Resources - Discussion threads, competitions, repositories, and other external references that can aid you in your quest.

For other platforms check out the sections here: