Skip to main content
Code Golf

Return to Answer

added 7 characters in body
Source Link
Wheat Wizard Mod
Wheat Wizard Mod
  • 100k
  • 1
  • 41
  • 84

No change in rules is needed, simply a change in behavior

This isn'tmight not be a complete answer, but I would like to provide what I think is a solution to the issues that doesn't actually require changing any rules.

First lets talk about weird and unpleasant formatting.

Rydwolf points out that there aren't currently any rules that require you to format your header in a particular way. In fact there is a consensus that there are no rules.

So currently people do have the freedom to write "8 trits", "19 Nibbles", or "2.99999999999 bytes". They just aren't. Changing the rules might encourage them to write differently. But seeing as this formatting is so widely disliked, I think making it clear that it is allowed to format in other, more pleasant ways, and giving some encouragement to do so will be enough to shift the way people format it.

Now lets talk about non-fractional byte things.

There's no rule that says you can't golf in codels either. Our rules do say that:

Answers that produce correct results, comply with the rules of the challenge, but aren't a serious contender for the winning criteria [1]

should be deleted.

However we've also been clear that:

A serious contender is a submission which makes a serious effort towards optimizing the submission's score within the chosen language(s) and other choices (such as algorithm choice or optional restrictions/bonuses taken).[2]

I think it is pretty straightforward to take away from this that yes you can golf with a different score than bytes in mind. "The program is going to optimize this metric" is a self-imposed restriction.

And as long as your scoring goal is conducive to shorter programs, and it seems all the interesting ones are, I don't see any rules actually being broken. Sure you might be able to get a shorter program by optimizing for bytes, but that would violate your restriction, so there's no requirement to do it.

Since, as previously stated, there's no requirement to put your byte count in the header you can put that score in the header. If someone asks for the byte count, I would suggest providing it to them, but that's just general courtesy.

The same applies here as the last one, just because something is allowed by the rules doesn't mean that everyone is taking advantage of it. But hopefully if we are clear that this is allowed, either through a rule change or just general communication people will change. Or maybe they won't, that's also fine, people can certainly continue to golf in bytes if that's what they prefer.

No change in rules is needed, simply a change in behavior

This isn't a complete answer, but I would like to provide what I think is a solution to the issues that doesn't actually require changing any rules.

First lets talk about weird and unpleasant formatting.

Rydwolf points out that there aren't currently any rules that require you to format your header in a particular way. In fact there is a consensus that there are no rules.

So currently people do have the freedom to write "8 trits", "19 Nibbles", or "2.99999999999 bytes". They just aren't. Changing the rules might encourage them to write differently. But seeing as this formatting is so widely disliked, I think making it clear that it is allowed to format in other, more pleasant ways, and giving some encouragement to do so will be enough to shift the way people format it.

Now lets talk about non-fractional byte things.

There's no rule that says you can't golf in codels either. Our rules do say that:

Answers that produce correct results, comply with the rules of the challenge, but aren't a serious contender for the winning criteria [1]

should be deleted.

However we've also been clear that:

A serious contender is a submission which makes a serious effort towards optimizing the submission's score within the chosen language(s) and other choices (such as algorithm choice or optional restrictions/bonuses taken).[2]

I think it is pretty straightforward to take away from this that yes you can golf with a different score than bytes in mind. "The program is going to optimize this metric" is a self-imposed restriction.

And as long as your scoring goal is conducive to shorter programs, and it seems all the interesting ones are, I don't see any rules actually being broken. Sure you might be able to get a shorter program by optimizing for bytes, but that would violate your restriction, so there's no requirement to do it.

Since, as previously stated, there's no requirement to put your byte count in the header you can put that score in the header. If someone asks for the byte count, I would suggest providing it to them, but that's just general courtesy.

The same applies here as the last one, just because something is allowed by the rules doesn't mean that everyone is taking advantage of it. But hopefully if we are clear that this is allowed, either through a rule change or just general communication people will change. Or maybe they won't, that's also fine, people can certainly continue to golf in bytes if that's what they prefer.

No change in rules is needed, simply a change in behavior

This might not be a complete answer, but I would like to provide what I think is a solution to the issues that doesn't actually require changing any rules.

First lets talk about weird and unpleasant formatting.

Rydwolf points out that there aren't currently any rules that require you to format your header in a particular way. In fact there is a consensus that there are no rules.

So currently people do have the freedom to write "8 trits", "19 Nibbles", or "2.99999999999 bytes". They just aren't. Changing the rules might encourage them to write differently. But seeing as this formatting is so widely disliked, I think making it clear that it is allowed to format in other, more pleasant ways, and giving some encouragement to do so will be enough to shift the way people format it.

Now lets talk about non-fractional byte things.

There's no rule that says you can't golf in codels either. Our rules do say that:

Answers that produce correct results, comply with the rules of the challenge, but aren't a serious contender for the winning criteria [1]

should be deleted.

However we've also been clear that:

A serious contender is a submission which makes a serious effort towards optimizing the submission's score within the chosen language(s) and other choices (such as algorithm choice or optional restrictions/bonuses taken).[2]

I think it is pretty straightforward to take away from this that yes you can golf with a different score than bytes in mind. "The program is going to optimize this metric" is a self-imposed restriction.

And as long as your scoring goal is conducive to shorter programs, and it seems all the interesting ones are, I don't see any rules actually being broken. Sure you might be able to get a shorter program by optimizing for bytes, but that would violate your restriction, so there's no requirement to do it.

Since, as previously stated, there's no requirement to put your byte count in the header you can put that score in the header. If someone asks for the byte count, I would suggest providing it to them, but that's just general courtesy.

The same applies here as the last one, just because something is allowed by the rules doesn't mean that everyone is taking advantage of it. But hopefully if we are clear that this is allowed, either through a rule change or just general communication people will change. Or maybe they won't, that's also fine, people can certainly continue to golf in bytes if that's what they prefer.

Source Link
Wheat Wizard Mod
Wheat Wizard Mod
  • 100k
  • 1
  • 41
  • 84

No change in rules is needed, simply a change in behavior

This isn't a complete answer, but I would like to provide what I think is a solution to the issues that doesn't actually require changing any rules.

First lets talk about weird and unpleasant formatting.

Rydwolf points out that there aren't currently any rules that require you to format your header in a particular way. In fact there is a consensus that there are no rules.

So currently people do have the freedom to write "8 trits", "19 Nibbles", or "2.99999999999 bytes". They just aren't. Changing the rules might encourage them to write differently. But seeing as this formatting is so widely disliked, I think making it clear that it is allowed to format in other, more pleasant ways, and giving some encouragement to do so will be enough to shift the way people format it.

Now lets talk about non-fractional byte things.

There's no rule that says you can't golf in codels either. Our rules do say that:

Answers that produce correct results, comply with the rules of the challenge, but aren't a serious contender for the winning criteria [1]

should be deleted.

However we've also been clear that:

A serious contender is a submission which makes a serious effort towards optimizing the submission's score within the chosen language(s) and other choices (such as algorithm choice or optional restrictions/bonuses taken).[2]

I think it is pretty straightforward to take away from this that yes you can golf with a different score than bytes in mind. "The program is going to optimize this metric" is a self-imposed restriction.

And as long as your scoring goal is conducive to shorter programs, and it seems all the interesting ones are, I don't see any rules actually being broken. Sure you might be able to get a shorter program by optimizing for bytes, but that would violate your restriction, so there's no requirement to do it.

Since, as previously stated, there's no requirement to put your byte count in the header you can put that score in the header. If someone asks for the byte count, I would suggest providing it to them, but that's just general courtesy.

The same applies here as the last one, just because something is allowed by the rules doesn't mean that everyone is taking advantage of it. But hopefully if we are clear that this is allowed, either through a rule change or just general communication people will change. Or maybe they won't, that's also fine, people can certainly continue to golf in bytes if that's what they prefer.