Difference between revisions of "Main Page"

From SizeCoding
Jump to: navigation, search
 
(26 intermediate revisions by the same user 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 most popular types of CPUs. As sizecoding is also popular on other hardware, we recently opened the website for other platforms as well, check the links below.''' 
+
'''SizeCoding.org''' is a wiki dedicated to teaching programmers the various techniques used to create [https://nanogems.demozoo.org/ tiny demoscene intros]. While these techniques can be used for other applications (boot sectors, ROM, BIOS and firmware code, etc.), the information presented here is firmly oriented towards the [https://en.wikipedia.org/wiki/Demoscene demoscene]. Practicality and common sense are sometimes thrown out the window just to shave a single byte.
  
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 an executable binary. 
+
For those unfamiliar with the demoscene or demoscene effects, here is:
 +
*'''[https://nanogems.demozoo.org/ A curated collection of the best Tiny Intros from the Demoscene]'''
 +
*'''[[Design Tips and Demoscene effects with pseudo code]]'''
 +
*'''[[Information about demoscene parties]]'''
  
'''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 just '''16 bytes'''  [https://demozoo.org/productions/?platform=&production_type=55] or even '''8 bytes''' [https://demozoo.org/productions/?platform=&production_type=54].
+
Now with that said, here is the list of active platforms available on this wiki:
  
'''The intent of this wiki is to teach assembler programmers the various techniques used to create tiny demoscene intros.'''
+
'''Oldschool 8-bit / 16-bit platforms:'''
While these techniques can be used for other applications (boot sectors, ROM, 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.
+
*'''[[Motorola 68000]]''' - [[Commodore_Amiga]], [[Atari_ST]], [[Spectrum_QL]], [[X68000]], etc.
 
 
Here is the list of active platforms available on this wiki:
 
 
 
Oldschool 8-bit / 16-bit platforms:
 
*'''[[Motorola 68000]]''' - Commodore Amiga, Atari ST, Atari Jaguar, Spectrum QL, Sharp X68000, etc.
 
 
*'''[[6502]]''' - Commodore 64, Atari XE/XL, Apple II, Atari Lynx, BBC Micro, etc.
 
*'''[[6502]]''' - Commodore 64, Atari XE/XL, Apple II, Atari Lynx, BBC Micro, etc.
 
*'''[[Z80]]''' - ZX Spectrum, Amstrad CPC, etc.
 
*'''[[Z80]]''' - ZX Spectrum, Amstrad CPC, etc.
Line 19: Line 17:
 
*'''[[PDP-11]]''' - BK-0010 / BK-0011, etc.
 
*'''[[PDP-11]]''' - BK-0010 / BK-0011, etc.
  
As well as modern platforms like:
+
 
*'''[[Fantasy consoles]]''' - Fantasy Consoles (TIC-80, PICO-8, MicroW8)
+
'''As well as modern platforms like:'''
*'''[[Windows]]''' - Sizecoding for Windows (1K and 4K intros).
+
*'''[[Fantasy consoles]]''' - [[TIC-80]], [[PICO-8]], [[MicroW8]]
 +
*'''[[Windows]]''' - Sizecoding for Windows: 1K and 4K intros.
 +
*'''[[DOS]]''' - Sizecoding for X86 / DOS.
 
*'''[[Javascript]]''' - Sizecoding for Browsers / JavaScript
 
*'''[[Javascript]]''' - Sizecoding for Browsers / JavaScript
 +
*'''[[Processing]]''' - Sizecoding using Processing
 
*'''[[Linux]]''' - Sizecoding for Linux.
 
*'''[[Linux]]''' - Sizecoding for Linux.
*'''[[DOS]]''' - Sizecoding for X86 / DOS.
 
 
*'''[[ARM]]''' - ARM-based platforms (RISC OS, Acorn Archimedes, Gameboy Advance, etc.)
 
*'''[[ARM]]''' - ARM-based platforms (RISC OS, Acorn Archimedes, Gameboy Advance, etc.)
 
*'''[[RISC-V]]''' - RISC−V micro-processors.  
 
*'''[[RISC-V]]''' - RISC−V micro-processors.  
*'''[[Processing]]''' - Sizecoding using Processing
 
 
*'''[[ReGIS]]''' - VT125, VT230, VT240/241 and more terminal display vector graphics language.
 
*'''[[ReGIS]]''' - VT125, VT230, VT240/241 and more terminal display vector graphics language.
 
*'''[[Bytebeat]]''' - Tiny music created from mathematical expressions.
 
*'''[[Bytebeat]]''' - Tiny music created from mathematical expressions.
 +
 +
By "very tiny programs", we usually mean programs that are '''1024 bytes or less in size''', typically created by members of the [https://en.wikipedia.org/wiki/Demoscene demoscene] as a show of programming skill. In other scenes this artform is sometimes also known as generative , codeart , proceduralart , generativeart , codegolfing , codegolf , tweetcart dwitter , twigl and tweetjam.
 +
 +
The size of these tiny programs is measured by their total size in opcode bytes, and are usually presented as an executable binary. 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 just '''16 bytes'''  [https://demozoo.org/productions/?platform=&production_type=55] or even '''8 bytes''' [https://demozoo.org/productions/?platform=&production_type=54].

Latest revision as of 16:21, 8 June 2025

Welcome to SizeCoding.org!

SizeCoding.org is a wiki dedicated to teaching programmers the various techniques used to create tiny demoscene intros. While these techniques can be used for other applications (boot sectors, ROM, 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.

For those unfamiliar with the demoscene or demoscene effects, here is:

Now with that said, here is the list of active platforms available on this wiki:

Oldschool 8-bit / 16-bit platforms:


As well as modern platforms like:

  • Fantasy consoles - TIC-80, PICO-8, MicroW8
  • Windows - Sizecoding for Windows: 1K and 4K intros.
  • DOS - Sizecoding for X86 / DOS.
  • Javascript - Sizecoding for Browsers / JavaScript
  • Processing - Sizecoding using Processing
  • Linux - Sizecoding for Linux.
  • ARM - ARM-based platforms (RISC OS, Acorn Archimedes, Gameboy Advance, etc.)
  • RISC-V - RISC−V micro-processors.
  • ReGIS - VT125, VT230, VT240/241 and more terminal display vector graphics language.
  • Bytebeat - Tiny music created from mathematical expressions.

By "very tiny programs", we usually mean programs that are 1024 bytes or less in size, typically created by members of the demoscene as a show of programming skill. In other scenes this artform is sometimes also known as generative , codeart , proceduralart , generativeart , codegolfing , codegolf , tweetcart dwitter , twigl and tweetjam.

The size of these tiny programs is measured by their total size in opcode bytes, and are usually presented as an executable binary. 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 just 16 bytes [1] or even 8 bytes [2].