Slow Computing Speedrunning: Difference between revisions
m (Fix broken link) |
(Minor cleanup of some typos, and clarifying some wording ~Sarah) |
||
| Line 6: | Line 6: | ||
It's pretty simple: | It's pretty simple: | ||
* Using any vintage computer of your choice, perform a | * Using any vintage computer of your choice, perform a long-running task of some sort | ||
* Livestream, or otherwise provide regular status updates that show how far you have gotten. | * Livestream, or otherwise provide regular status updates that show how far you have gotten. | ||
* Emulators and the like are A-OK; just let us know what | * Emulators and the like are A-OK; just let us know what it's doing. | ||
After each run, success or failure, our judges (which is mostly just the regulars in #paint-drying on [http://discord.gg/V8esNah Discord]) will deem what, if any titles such run has earned, and an entirely subjective place on the Wall of Pain. There are absolutely no prizes besides the knowledge that you might be immortalized here for the life of the wiki. | After each run, success or failure, our judges (which is mostly just the regulars in #paint-drying on [http://discord.gg/V8esNah Discord]) will deem what, if any titles such run has earned, and an entirely subjective place on the Wall of Pain. There are absolutely no prizes besides the knowledge that you might be immortalized here for the life of the wiki. | ||
Do you dare step up | Do you dare step up? | ||
=== Examples of projects === | === Examples of projects === | ||
For example, upgrading through every version of OS/2, building GCC, or the like. Livestream or otherwise regularly update the panting drying competition community. For NCommander's | For example, upgrading through every version of OS/2, building GCC, or the like. Livestream or otherwise regularly update the panting drying competition community. For NCommander's entries, VoDs on YouTube were provided. Europa livestreamed the terminal on Discord throughout the duration. Any sorta long running log with regular updates is acceptable. | ||
= The Wall of Pain = | = The Wall of Pain = | ||
| Line 21: | Line 21: | ||
== Idle Pain == | == Idle Pain == | ||
Idle | Idle Pain refers to tasks where they're started, and mostly left untouched until they finish (excluding minor tweaks, build failures, etc.) | ||
=== GCC 8 on an Ultra 5 running OpenBSD/sparc64 (Europa) === | === GCC 8 on an Ultra 5 running OpenBSD/sparc64 (Europa) === | ||
| Line 31: | Line 31: | ||
== Active Pain == | == Active Pain == | ||
Active Pain | Active Pain entries are livestreams or single projects that are actively worked on over the period of the competition. They can be over multiple sessions, with time being tallied up. | ||
=== Upgrading Through Every Version of OS/2 (NCommander) === | === Upgrading Through Every Version of OS/2 (NCommander) === | ||
Revision as of 01:53, 7 November 2022
Welcome to the Slow Computing any% Speedrunning Contest; also known as watching digital paint dry.
The goal of this contest is simple. To celebrate the long code [1] times, we're running an informal contest to celebrate this era of batch processing.
Objective and Rules
It's pretty simple:
- Using any vintage computer of your choice, perform a long-running task of some sort
- Livestream, or otherwise provide regular status updates that show how far you have gotten.
- Emulators and the like are A-OK; just let us know what it's doing.
After each run, success or failure, our judges (which is mostly just the regulars in #paint-drying on Discord) will deem what, if any titles such run has earned, and an entirely subjective place on the Wall of Pain. There are absolutely no prizes besides the knowledge that you might be immortalized here for the life of the wiki.
Do you dare step up?
Examples of projects
For example, upgrading through every version of OS/2, building GCC, or the like. Livestream or otherwise regularly update the panting drying competition community. For NCommander's entries, VoDs on YouTube were provided. Europa livestreamed the terminal on Discord throughout the duration. Any sorta long running log with regular updates is acceptable.
The Wall of Pain
New categories will be added as needed
Idle Pain
Idle Pain refers to tasks where they're started, and mostly left untouched until they finish (excluding minor tweaks, build failures, etc.)
GCC 8 on an Ultra 5 running OpenBSD/sparc64 (Europa)
- Status:: Ongoing
- Duration: 3+ days (ongoing)
- Proof: Livestreamed on Discord
- Comments:
- The build that started it all, Europa's attempt to install CDE which required upgrading GCC, and starting a multiday build process that lead to the creation of the paint drying community ... I'm still wondering how we got here - NCommander (talk) 14:54, 4 November 2022 (UTC)
Active Pain
Active Pain entries are livestreams or single projects that are actively worked on over the period of the competition. They can be over multiple sessions, with time being tallied up.
Upgrading Through Every Version of OS/2 (NCommander)
- Status: Complete/Historical
- .Proof: VoDs: https://www.youtube.com/watch?v=xeaRlhz96mI and https://www.youtube.com/watch?v=8uwGTHZzzF4
- Duration: Approximately 22 Hours
- Comments:
- ow - NCommander (talk) 14:54, 4 November 2022 (UTC)