-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The Shortest NaNoGenMo Entry You'll Probably See #69
Comments
Now you're probably wondering "how is that 40 bytes? The utf-8 byte counter I use says it's 72 bytes. And what on earth is up with all those garbage characters?" |
Well for a start, this novel generating program is written using an esoteric programming language (esolang) called Vyxal (disclaimer: I made the language lol). It is designed to perform well in code golf competitions on the Code Golf StackExchange site - as such, it's known as what's called a "golfing language". There are various other golfing languages such as Golfscript, 05AB1E, Jelly and Husk. In languages such as these, each command (built-in) is a single character/byte. |
(Note that the writeup for this is still WIP/as a draft - I'll be adding more soon. I just wanted to make sure I got #69 because it's a funny number) |
(Also, if I've submitted this wrong, let me know the best way to actually submit it) |
This is the right way to submit, it would be good to post a static 50k+ output somewhere when you're ready. There's a name for these microprograms: Nano-NaNoGenMo!
|
Wow, look at everyone else writing generating programs that span multiple lines. Sure, they have fancy "markov chain" or "special filter" rules that make the generated novel make more sense and make the program longer, but as a green cucumber once said, "in the future, humour will be randomly generated". Therefore, I present to you a program that will randomly generate 50000 word novels using only
4140 bytes.Try it Online! (it'll probably timeout, but that's fine).
The text was updated successfully, but these errors were encountered: