- To write the most Transcendental, Imbroglio Ruby program.
- To illustrate some of the subtleties (and design issues) of Ruby.
- To show the robustness and portability of Ruby interpreters.
- To stabilize the spec of Ruby by the presence of valuable but unmaintainable code.
These rules are tentative.
- Your entry must be a complete Ruby program.
- The size of your program must be <= 4096 bytes in length. The number of non-space characters must be <= 2048. The total size of your compressed submission must be less than 10 MB.
- You can submit multiple entries, and your team may consist of any number of members.
- The entirety of your entry must be submitted under MIT License.
- Your entry must bring the judges a surprise, excitement, and/or laughter.
These are not strict rules but hints or suggestions. You can ignore them but we'd recommend you to follow them.
- Matz Ruby Implementation (MRI) 3.3 or 3.4 is recommended.
- You can use implementations other than MRI, such as JRuby and TruffleRuby.
- The judges would prefer more stoic, more portable, and/or more funny entries.
- You are encouraged to study the winners of previous TRICK contests.
- You can use gem libraries.
- Note that we will expect such entries to be much more interesting than an entry that uses no library; hence we will judge them strictly.
- It is highly discouraged to abuse gem to get around the size limit.
- To judge without bias, we will try to keep each entry anonymous during judgment. Do not include anything that reveal your identity (such as a signature, copyright, URL, etc.) in your program.
- (NEW) You can use ruby.wasm.
- Please elaborate how to run in
remarks.markdown
. - If your entry works on browser, please include .html and (if any) .js and media files in your submission.
- You don't have to include .html and .js in the code size limit (up to 4096 bytes). But it would be cool if they fit in total.
- Please care the total size limit (up to 10 MB).
- It is ok to use ruby.wasm on CDN by a
<script>
tag. See the quick example of ruby.wasm. Using other files in the network is not recommended.
- If you have any question, please send a mail to
trick-judges at googlegroups.com
.
- Please elaborate how to run in
- Your submission must consist of the following files:
entry.rb
(program source)remarks.markdown
authors.markdown
Gemfile
,Gemfile.lock
(if you use any gem library)- data files (if needed)
remarks.markdown
must include the following information:- Ruby implementation, version, platform that you use (it is a good idea to copy and paste the output of
ruby -v
) - How to run
- Ruby implementation, version, platform that you use (it is a good idea to copy and paste the output of
authors.markdown
must include the following information (and theremarks.markdown
must NOT have them):- Your name (handle is ok)
- ccTLD of your country/region
- Compress your entry as a zip file called
entry.zip
and send it totrick.submit at gmail.com
as an attachment.- You must include the words
TRICK 2025 submission
in the subject of your email. - See an example of
entry.zip
.
- You must include the words
If you have any question, please send a mail to trick-judges at googlegroups.com
.
- August 31st, 2024: Contest open
- February 28th, 2025: Submission deadline
- April 15th--18th, 2025: Result announcement (in RubyKaigi 2025)
Alphabetical order.
- Yusuke Endoh (@mametter. Ruby committer. The world's No.1 IOCCC player.)
- Koichiro Eto (@eto. Media Artist. Chairman at NicoNicoGakkai Beta.)
- Shinichiro Hamaji (@shinh. The admin of anarchy golf. IOCCC winner.)
- Yutaka Hara (@yhara. The author of Japanese esolang book.)
- Tomoya Ishida (@tompng. The gold and silver medalist of TRICK 2022.)
- Yukihiro Matsumoto (a.k.a. matz. @yukihiro_matz. The creator of Ruby.)
- Sun Park (a.k.a. leonid. The 1st super Ruby golfer.)
- Darren Smith ([a.k.a. flagitious. The author of some esolangs including GolfScript.)
This work is licensed under the MIT License.
Copyright (c) 2024, TRICK Winners and Judges.
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.