Conversation started Jun 18, 2021 at 23:08.
lyxal
lyxal
Jun 18, 2021 23:08

I needed this bookmark for discussion purposes.

4 hours ago, 36 minutes total – 121 messages, 9 users, 5 stars

Bookmarked 5 secs ago by lyxal

Looks like there's been yet another flag bashing in the nineteenth byte
and people have one again thought of changing the flag counting rules
here's my response
I have said in the past that if flags weren't "free", I wouldn't use them
and I still hold to that today
if flags were made to have a byte penalty, I would stop using them
"but that would invalidate a good majority of answers" I hear you say
and you'd be right
except for the fact that "flags make a submission a different language"
If there was meta consensus that flags were a part of the byte count, I'd make a whole bunch of branches that are the equivalent of having flags
I'd make a j branch to simulate having the j flag, a r branch to simulate the r flag, and so on
and then there'd be things like a jr branch or a rjM branch for all the two flag and three flag combos
so the point is that flags help automate this process in a way
And for y'all saying that the fizzbuzz is 'cheating', well yes, it kind of is. But here's the thing...
I would still beat Jelly without the kF constant
kF simply helps get the score down even further
further
I still beat Jelly without the j flag and without kF
so next time someone complains about flags or compares the whole thing to metagolfscript (I've a certain scottish user in mind), link them to this
show them that flags aren't just making things up as we go
show them that flags are a somewhat natural part of code golf, as it's the Vyxal way of trying to get byte count down no matter what
 
Conversation ended Jun 18, 2021 at 23:20.