@WheatWizard You know, I remember adding the -r flag for backwards compatibility, not golf but it turns out it can save bytes too.
For example, since subtraction/decrementing is so inefficient compared to adding/incrementing, pushing a lot of descending numbers is a lot easier with the -r flag
Brain-Flak, 186 bytes
(((((((((((((((((((((((((((((((((()()()()()){})){}{}()){({}[()])}{})){}{})())())())())())())())())())()())[()])()())()())[()])()()())[()])()())())()())[()])()()())[()])()())())())())
This code is 182 bytes long, and I added 4 bytes for two command line flags: -r and -u
T...
@Riley Yeah, there's that. I also don't see any reason for -a -A -c to overwrite each other. Then treat input and output completely separate, and -c just happens to be an alias for -aA
I'm not sure how well that would work with utf though. Maybe have -u and -U and -C as an alias for -uU
But then you could run into some weird combos like -aU or -Au
A question worth asking is whether we want a separate ascii in and unicode in as ascii in is just unicode in but with errors for characters not with the 256 ascii characters
I'm not sure when that error checking would actually be useful
Brain-Flak, 172 + 4 = 176 bytes
This answer is based largely one DJMcMayhem's solution here so I recomend you check it out.
Like DJMcMayhem's solution this uses the -ru flag to reverse output and print to unicode.
Try it Online
(((((()()()()()){})))<(((({}{}{}()){({}[()])}{})){}{})>){({}[()]<...