Timeline for J and GolfScript suck all the enjoyment out of Code Golf
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 18, 2017 at 20:53 | comment | added | user233009 | True. I never saw that anywhere. I might try to make a question like that. | |
| Apr 18, 2017 at 8:11 | comment | added | Martin Ender Mod | This is basically equivalent to atomic-code-golf although it seems that you want to weight different operators depending on how much they do. You should be able to find several discussions about this or similar scoring mechanisms on meta. The general problem is that it's impossible to define this scoring in a fair and objective way across all possible languages. You'd have to come up with scoring rules for every single language separately which isn't really feasible. Atomic code golf works best if you instead define a toy language for the challenge that everyone has to use. | |
| Apr 18, 2017 at 7:51 | history | answered | user233009 | CC BY-SA 3.0 |