Adjudicated Blind Collaborative Design Esolang Factory

The Adjudicated Blind Collaborative Design Esolang Factory has the mission to create languages that make it easy to do things programmers want to do. The only solution to this problem is to let programmers decide what they want without being influenced by each other.

Current Factory Run

There is a factory run started by Jannis Harder at 20:20 GMT on the 21. October 2006. The email address to submit statements to is jannis@harderweb.de. Submissions should contain [Adjudicated Blind Collaborative Design Esolang Factory] in the Subject. Each mail should contain 5 to 15 statements (see rules). Statements will be accepted till 22:20 GMT on the 23. October 2006. You can reach the moderator using the submission email address or as jix on the Freenode irc network.

The current run has ended. The text of the submissions is at http://www.harderweb.de/tmp_jix/allofthem.txt (dead link)

Past Factory runs

None yet.

Rules

This section will describe the Rules according to the Adjudicated Blind Collaborative Design Esolang Factory Guidelines

The Moderator

The moderator is responsible for organizing a factory run. He collects the statement entries and has the final word on the language. The moderator should, when possible, lead the work of writing the first reference interpreter/compiler.

The Community

The community consists of all participants, including the moderator. Each member will submit a list of 5 to 15 statements to the moderator by email (except the moderator, who will write down his statements as first). All these statements will be given to the community for review. The next stage consists of discussing the statements and to decide what the language should look like (the main goal is to get all statements into the language) This is the task of the whole community, not of the moderator

The Specification

When the community agrees about the language, a specification has to be written. This is the task of the moderator, but the community is encouraged to help.

The Reference Implementation

What is a spec without an implementation? ... well a spec, but that isn't the point. The Factory should produce complete languages and the Adjudicated Blind Collaborative Design Esolang Factory Guidelines say that this includes a reference implementation. As this probably won't be easy the moderator should do this (as she/he is responsible for starting the whole mess). Of course, it won't hurt if members of the community help.

Statements

So, you ask, what are statements? The Adjudicated Blind Collaborative Design Esolang Factory Guidelines say that statements don't have to be statements in the classical imperative sense, but can be anything from operators over functions to assembler directives- there are effectively no limits.

Limitations

Well there are at least some limits but they are kept to a minimum. The Adjudicated Blind Collaborative Design Esolang Factory Guidelines say that each statement should be implementable on a standard modern computer (The specs may mention infinite memory but the implementation obviously can't do that). The other limitation is that the moderator may specify the source format (text file / binary file / picture etc...)

A Statement description should describe all side effects of the statement as well as the accurate syntax definition (when possible).

Origin

The idea of the Adjudicated Blind Collaborative Design Esolang Factory came from Jannis Harder. While reading through the INTERCAL specification he thought that no single person would be able to come up with such an obscure accumulation of statements.