Difference between revisions of "SizeCoding:About"
(→Doesn't in4k cover this material?) |
|||
| Line 11: | Line 11: | ||
== Doesn't in4k cover this material? == | == Doesn't in4k cover this material? == | ||
| − | in4k mostly concentrates on 1k and larger productions, across all environments (Windows, javascript, webgl, etc.). SizeCoding is much more targeted, and concentrates on 512b and lower, x86 only. | + | [https://in4k.github.io/ in4k] mostly concentrates on 1k and larger productions, across all environments (Windows, javascript, webgl, etc.). SizeCoding is much more targeted, and concentrates on 512b and lower, x86 only. |
Revision as of 11:35, 20 August 2016
History
sizecoding.org grew from a conversation between Trixter, HellMood, and qkumba when it was determined there was no central repository for sizecoding information. Trixter had inquired because VileR was dipping his toes into the lake that is sizecoding, and wanted to point him to a starting point for resources suitable for beginners. None existed, so Trixter stood up sizecoding.org, and all three of them contributed information and examples to the initial launch.
Many thanks to the entire demoscene for knowledge and inspiration.
Why a Wiki?
Wikis have the lowest barrier to entry for contributing to information stores. We encourage the entire demoscene and assembler programming community to contribute.
Doesn't in4k cover this material?
in4k mostly concentrates on 1k and larger productions, across all environments (Windows, javascript, webgl, etc.). SizeCoding is much more targeted, and concentrates on 512b and lower, x86 only.
