Timeline for J and GolfScript suck all the enjoyment out of Code Golf
Current License: CC BY-SA 3.0
33 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Sep 22, 2023 at 18:01 | comment | added | The Empty String Photographer | By today’s standards, 100 bytes is quite long. | |
Jun 23, 2017 at 21:55 | history | rollback | user62131 |
Rollback to Revision 3
|
|
Jun 23, 2017 at 16:29 | history | edited | Mr. Xcoder | CC BY-SA 3.0 |
wording tweaks
|
Apr 18, 2017 at 7:51 | answer | added | user233009 | timeline score: -6 | |
Nov 24, 2016 at 8:43 | comment | added | Esolanging Fruit | I read the first few words of this and I thought it said "J and GolfScript suck" :-) | |
Mar 14, 2016 at 23:09 | answer | added | xnor | timeline score: 27 | |
Jun 9, 2015 at 21:41 | answer | added | Rainbolt | timeline score: 15 | |
May 7, 2015 at 16:26 | answer | added | tfitzger | timeline score: 1 | |
Feb 24, 2014 at 0:49 | comment | added | TheDoctor | Don't forget about APL | |
Feb 23, 2014 at 19:33 | answer | added | Tobia | timeline score: 18 | |
Feb 21, 2014 at 15:48 | answer | added | Thomas Weller | timeline score: -1 | |
Feb 13, 2014 at 18:50 | answer | added | daniero | timeline score: 57 | |
Feb 13, 2014 at 16:24 | answer | added | Jonathan Van Matre | timeline score: 14 | |
Feb 1, 2014 at 21:57 | history | edited | Timwi | CC BY-SA 3.0 |
added 624 characters in body
|
Feb 1, 2014 at 20:25 | answer | added | Tomas | timeline score: 5 | |
May 15, 2011 at 18:22 | comment | added | zzzzBov | Two feature considerations that don't quite fit the stackexchange model: the ability to tag the programming language used in the answer, and subsequently, the ability to filter answers by programming language. | |
Apr 26, 2011 at 5:24 | answer | added | Gregory Higley | timeline score: 5 | |
Apr 23, 2011 at 22:28 | answer | added | Rei Miyasaka | timeline score: 2 | |
Apr 21, 2011 at 14:18 | comment | added | Scott | I completely agree. The length of the code is far less interesting to me than the speed and readability. | |
Apr 12, 2011 at 20:47 | answer | added | mrmekon | timeline score: 75 | |
Apr 12, 2011 at 1:17 | answer | added | user unknown | timeline score: 3 | |
Apr 6, 2011 at 6:18 | comment | added | Peter Taylor | The other problem with #1 is that you'll likely end up with lots of questions with only a single answer. See also #3. | |
Apr 5, 2011 at 23:17 | comment | added | gnibbler Mod | I can't see #1 working, there are just too many languages golf.shinh.org/lranking.rb has 83 to choose from. Are you suggesting we ask the same question 83 (or more) times for each language? | |
Apr 5, 2011 at 18:47 | answer | added | Eelvex | timeline score: 19 | |
Apr 5, 2011 at 18:05 | comment | added | Eelvex | We do have a serious voting problem. It seems like most people here wouldn't even bother to vote their own questions/answers. | |
Apr 5, 2011 at 12:50 | answer | added | aaaaaaaaaaaa | timeline score: 6 | |
Apr 4, 2011 at 22:57 | comment | added | dmckee --- ex-moderator kitten Mod | Many related questions/discussions: meta.codegolf.stackexchange.com/questions/185/language-handicap meta.codegolf.stackexchange.com/questions/67/… meta.codegolf.stackexchange.com/questions/88/… meta.codegolf.stackexchange.com/questions/9/… meta.codegolf.stackexchange.com/questions/127/… ... | |
Apr 4, 2011 at 21:06 | answer | added | gnibblerMod | timeline score: 12 | |
Apr 4, 2011 at 14:27 | comment | added | hallvabo | I think #2 is the solution, and that is what I do when I see Python answers. Maybe you need to recruit more C# golfers to the site? :-) | |
Apr 4, 2011 at 12:08 | answer | added | hallvabo | timeline score: 31 | |
Apr 4, 2011 at 12:00 | comment | added | YOU | For me, I've end up with learning Golfscript. | |
Apr 4, 2011 at 11:11 | history | edited | Jeff Atwood | CC BY-SA 2.5 |
edited tags
|
Apr 4, 2011 at 10:26 | history | asked | Timwi | CC BY-SA 2.5 |