Difference between revisions of "Main Page"
| Line 1: | Line 1: | ||
== Welcome to SizeCoding.org! == | == Welcome to SizeCoding.org! == | ||
| − | '''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. | + | '''SizeCoding.org''' is a wiki dedicated to teaching programmers the various techniques used to create [https://nanogems.demozoo.org/ tiny demoscene intros]. In other scenes this artform is sometimes also known as #generative #codeart #proceduralart #generativeart #codegolfing #codegolf #tweetcart #dwitter and #tweetjam. 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. |
| + | |||
| + | |||
For those unfamiliar with the demoscene or demoscene effects, here is: | For those unfamiliar with the demoscene or demoscene effects, here is: | ||
Revision as of 15:27, 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. In other scenes this artform is sometimes also known as #generative #codeart #proceduralart #generativeart #codegolfing #codegolf #tweetcart #dwitter and #tweetjam. 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:
- A curated collection of the best Tiny Intros from the Demoscene
- Information about demoscene parties
- A list of demoscene effects with pseudo code
Now with that said, here is the list of active platforms available on this wiki:
Oldschool 8-bit / 16-bit platforms:
- Motorola 68000 - Commodore_Amiga, Atari_ST, Spectrum_QL, X68000, etc.
- 6502 - Commodore 64, Atari XE/XL, Apple II, Atari Lynx, BBC Micro, etc.
- Z80 - ZX Spectrum, Amstrad CPC, etc.
- 6809 - Dragon 32/64, Tandy CoCo, Vectrex, etc.
- PDP-11 - BK-0010 / BK-0011, etc.
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. 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].
