Timeline for The Squiggly Sequence
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:39 | history | edited | CommunityBot |
replaced http://codegolf.stackexchange.com/ with https://codegolf.stackexchange.com/
|
|
| Sep 2, 2016 at 5:25 | history | edited | DLosc | CC BY-SA 3.0 |
Corrected Pyth explanation
|
| Sep 2, 2016 at 4:26 | comment | added | Maltysen | pyth doesn't have implicit point free syntax. it works pretty much the same way it does in python, making it readable yet short. your comment about the unbalanced delimiters on the other hand is pretty true | |
| Sep 1, 2016 at 0:52 | comment | added | DLosc | @Cyoce chat.stackexchange.com/transcript/message/31933195 | |
| Aug 31, 2016 at 22:50 | comment | added | Cyoce | Pro tip for making a golfing language: don't use infix | |
| Aug 31, 2016 at 15:59 | comment | added | DLosc |
@GreenAsJade I expect a lot of people feel the same. I would just make one distinction: code golf != golflang design. Now you may well argue that the same principle (shorter is always better) applies to language design too. I'm just saying that for me, usability and even aesthetics are considerations.
|
|
| Aug 31, 2016 at 11:02 | comment | added | GreenAsJade | I'm not sure that readability is a plus, in code golf? Not at the cost of bytes ! | |
| Aug 31, 2016 at 5:09 | history | answered | DLosc | CC BY-SA 3.0 |