Difference between revisions of "Main Page"
From SizeCoding
| (15 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 most popular types of CPUs. As sizecoding is also popular on other hardware we recently opened the website for other | + | '''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.''' |
| − | 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. | + | 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. |
| − | '''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 just '''16 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 just '''16 bytes''' [https://demozoo.org/productions/?platform=&production_type=55] or even '''8 bytes''' [https://demozoo.org/productions/?platform=&production_type=54]. |
| − | '''The intent of this wiki is to teach assembler programmers the various techniques used to create tiny demoscene intros.''' | + | '''The intent of this wiki is to teach assembler 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. Consider yourself warned. | ||
| − | + | Here is the list of active platforms available on this wiki: | |
| − | *'''[[ | + | *'''[[Windows]]''' - Sizecoding for Windows. |
| − | + | *'''[[Linux]]''' - Sizecoding for Linux. | |
| − | *'''[[ | + | *'''[[Javascript]]''' - Sizecoding for Browsers / JavaScript |
| − | + | *'''[[Fantasy consoles]]''' - Fantasy Consoles (TIC-80 , PICO-8, MicroW8) | |
| − | *'''[[ | + | *'''[[DOS]]''' - Sizecoding for X86 / DOS. |
| − | + | *'''[[ARM]]''' - ARM-based platforms (RISC OS, Acorn Archimedes, Gameboy Advance, etc.) | |
| − | *'''[[ | + | *'''[[RISC-V]]''' - RISC−V micro-processors. |
| + | *'''[[Processing]]''' - Sizecoding using Processing | ||
| + | *'''[[ReGIS]]''' - VT125, VT230, VT240/241 and more terminal display vector graphics language. | ||
| + | *'''[[Bytebeat]]''' - Tiny music created from mathematical expressions. | ||
| − | + | 8-bit and 16-bit platforms: | |
| − | + | *'''[[Motorola 68000]]''' - Commodore Amiga, Atari ST, Atari Jaguar, Spectrum QL, etc. | |
| − | *'''[[ | + | *'''[[6502]]''' - Commodore 64, Atari XE/XL, Apple II, Atari Lynx, BBC Micro, etc. |
| − | + | *'''[[Z80]]''' - ZX Spectrum, Amstrad CPC, etc. | |
| − | + | *'''[[PDP-11]]''' - BK-0010 / BK-0011, etc. | |
| − | *'''[[6502 | + | *'''[[6809]]''' - Dragon 32/64, Tandy CoCo, Vectrex, etc. |
| − | *'''[[Z80 | ||
| − | *'''[[PDP-11 | ||
| − | |||
| − | *'''[[ | ||
| − | |||
Latest revision as of 04:31, 15 April 2024
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.
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 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].
The intent of this wiki is to teach assembler 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. Consider yourself warned.
Here is the list of active platforms available on this wiki:
- Windows - Sizecoding for Windows.
- Linux - Sizecoding for Linux.
- Javascript - Sizecoding for Browsers / JavaScript
- Fantasy consoles - Fantasy Consoles (TIC-80 , PICO-8, MicroW8)
- DOS - Sizecoding for X86 / DOS.
- ARM - ARM-based platforms (RISC OS, Acorn Archimedes, Gameboy Advance, etc.)
- RISC-V - RISC−V micro-processors.
- Processing - Sizecoding using Processing
- ReGIS - VT125, VT230, VT240/241 and more terminal display vector graphics language.
- Bytebeat - Tiny music created from mathematical expressions.
8-bit and 16-bit platforms:
- Motorola 68000 - Commodore Amiga, Atari ST, Atari Jaguar, Spectrum QL, etc.
- 6502 - Commodore 64, Atari XE/XL, Apple II, Atari Lynx, BBC Micro, etc.
- Z80 - ZX Spectrum, Amstrad CPC, etc.
- PDP-11 - BK-0010 / BK-0011, etc.
- 6809 - Dragon 32/64, Tandy CoCo, Vectrex, etc.
