Skip to main content
We’ve updated our Terms of Service. A new AI Addendum clarifies how Stack Overflow utilizes AI interactions.
Code Golf

Timeline for Who wants to be a Kolmogorov complexity winner?

Current License: CC BY-SA 3.0

34 events
when toggle format what by license comment
Apr 13, 2017 at 12:39 history edited Community Bot
replaced http://codegolf.stackexchange.com/ with https://codegolf.stackexchange.com/
Oct 28, 2015 at 23:52 answer added The Fifth Marshal timeline score: 1
Oct 31, 2014 at 21:45 answer added nneonneo timeline score: 2
Jul 26, 2014 at 17:55 answer added hlt timeline score: 5
Jul 20, 2014 at 7:32 history edited xem CC BY-SA 3.0
added 6 characters in body
Jul 19, 2014 at 22:12 answer added gxtaillon timeline score: 6
Jul 19, 2014 at 7:05 history edited xem CC BY-SA 3.0
added 140 characters in body
Jul 19, 2014 at 7:01 comment added xem @Milo & gxtaillon, I've made this point clearer: use the encoding that you want.
Jul 19, 2014 at 6:59 comment added xem @moogie no particular order, you should pack them separately
Jul 19, 2014 at 6:58 comment added xem Hi all, I've edited all the question, it's now a code-golf challenge. The size of your code counts in the score. I've clearly explained which input and output are expected and I've provided the dictionnary as an array of strings, if anyoune needs it.
Jul 19, 2014 at 6:53 history edited xem CC BY-SA 3.0
added 41 characters in body; edited tags
Jul 19, 2014 at 6:41 history edited xem CC BY-SA 3.0
added 7112 characters in body
Jul 19, 2014 at 4:16 comment added Moogie @xem what order should the snippets be output? better yet, instead of listing the links to the snippets, please provide the official expected output.
Jul 19, 2014 at 2:17 comment added Milo @gxtaillon well it changes the characters we can use. Our input is 0-127 but our output is much larger because U+10FFFF is UTF-32 only I am pretty sure. Unless you use four UTF-8 unicode characters to make one UTF-32
Jul 19, 2014 at 1:40 comment added gxtaillon @Milo I do not think so since the score is based on the number of unicode characters of the encoded output. UTF8 to UTF32 would have no effect on the score.
Jul 19, 2014 at 0:52 comment added Milo UTF8 to UTF32 correct?
Jul 18, 2014 at 21:30 comment added Rainbolt @xem I think the post could be improved by organizing the information into sections such like #Task, #Input, #Output, #Scoring. I also think that the size of the source code for the compressor and the decompressor should be included in the score. This doesn't hurt anything, but it solves the problem Dennis pointed out.
Jul 18, 2014 at 20:16 review Close votes
Jul 19, 2014 at 0:47
Jul 18, 2014 at 20:00 comment added Peter Taylor I don't think you've addressed Dennis' observation.
Jul 18, 2014 at 18:08 history tweeted twitter.com/#!/StackCodeGolf/status/490196347480711169
Jul 18, 2014 at 17:37 comment added xem Hey guys, I've made the rules clearer (I hope) by providing an authorized dictionnary of english words. People can use it in their packer/unpacker, but they can't use any other external input. Hope this helps.
Jul 18, 2014 at 17:34 history reopened Qeole
nderscore
Timtech
William Barbosa
xem
Jul 18, 2014 at 17:34 history edited xem CC BY-SA 3.0
added 102 characters in body
Jul 18, 2014 at 5:57 review Reopen votes
Jul 18, 2014 at 17:37
Jul 18, 2014 at 5:40 comment added xem Okay, I removed the mention of "language". now it's just a packer/unpacker.
Jul 18, 2014 at 5:38 history edited xem CC BY-SA 3.0
deleted 273 characters in body
Jul 18, 2014 at 5:36 history closed Kyle Kanos
William Barbosa
Glenn Randers-Pehrson
Paul Prestidge
algorithmshark
Needs more focus
Jul 18, 2014 at 2:36 comment added histocrat To make it a real language creation challenge, maybe specify that it has to be Turing-complete and the executor can't use "eval" or similar.
Jul 18, 2014 at 0:16 comment added Graph Theory Darn, and here I was already typing private static final String RICK_ROLL_RETURN = "We're no strangers to love...
Jul 17, 2014 at 23:29 review Close votes
Jul 18, 2014 at 5:36
Jul 17, 2014 at 23:12 comment added Dennis I think not including the size of the compiler/executor (compressor/decompressor) in the score makes this challenge a little open-ended. At some point, the line between dictionary and hard-coding will become very thin.
Jul 17, 2014 at 21:56 comment added Justin This isn't a challenge to invent a language, this is a challenge to compress something.
Jul 17, 2014 at 21:48 comment added Claudiu Not immediately obvious how this is a programming language. The 'compiler' doesn't take source code. I guess rather it creates a program which is then interpreted
Jul 17, 2014 at 21:13 history asked xem CC BY-SA 3.0
toggle format

AltStyle によって変換されたページ (->オリジナル) /