Hey guys so I was looking around the HTML of SE Chat uisng dev tools and found something cool ROs can do. Apparently there's a kind of RO-Script that exists that allows you to perform chat commands using JS-like syntax. Watch:
let TNB = network.sites["code golf"].rooms[240];
let lyxal = network.users[354515];
TNB.setName("The " + numToWord(lyxal.age++).uppercase() + "th Byte");
See? The name of this room is now the result of the RO-Script I ran.
A twin of this.
FizzBuzz is where a range of positive integers is taken, and numbers divisible by 3 are replaced with "Fizz", divisible by 5 with "Buzz" and divisible by 15 with "FizzBuzz". For example, FizzBuzz from 1 to 10 is 1, 2, Fizz, 4, Buzz, Fizz, 7, 8, Fizz, Buzz.
Your challenge is to, gi...
And they make languages more boring both to design and golf in
Golfing language design involves lots of hard choices, using a flag to get rid of those is a lazy and indecisive middle option that gives you an excuse not to innovate
I'm now more or less okay with flags from a scoring perspective, but I still consider actively choosing to add them to either be a boring design choice or a cringe attempt at being edgy in most cases
For languages that already have them, like Vyxal and Japt, there isn't any particular amount of harm, but I'd rather flags not become a standard part of the golflang dev's toolkit, otherwise we'll see "innovation" that gradually pushes closer and closer to MGS and farther from the intended goal of the flag rule, which was fairer scoring
(fairer mostly within languages, fairness across languages doesn't particularly matter for reasons I brought up yesterday)
@RadvylfPrograms I see them as more of a "just-in-case" thing. Like when you make a design decision that is generally a good decision but you want to make sure you don't get caught out on those edge cases where it would have otherwise helped
Get multi-dimensional indices in a list
code-golf array
Given a matrix of non-negative numbers (of arbitrary dimension) and a number, get all multi-dimensional indices of the number in that list.
For example, let's say we have the list [[0,1,0],[1,0,0]] and the number 1. In the first list, we see...
Why you should write a kernel in brainfuck: 1. It's very safe; all errors are caught at compile time 2. It's turing complete 3. The lack of complicated operations allows for easier optimization, and the tape is good for cache locality 4. It effortlessly works cross-platform
Find the best character arrangement
grid optimization fastest-code
You want to write your English essay. However, all characters on your keyboard broke other than the arrow keys and the enter key. You want to find out how to place the characters so you can write your essay with the least movement...
Goal
You have to print the ASCII printable characters' code page (0x20-0x7E).
The output should look like this:
!"#$%&'()*+,-./
0123456789:;<=>?
@ABCDEFGHIJKLMNO
PQRSTUVWXYZ[\]^_
`abcdefghijklmno
pqrstuvwxyz{|}~
Rules
The output should be exactly like shown above, but one trailing newline is O...
Cognate
Cognate is a stack-based programming language designed to be readable as English.
Uniquely among stack-based languages, it evaluates right-to-left. This means you can write code more naturally like English:
Print "Hello, World!"
Cognate allows you to write arbitrary words in between comm...
CMM: Should we have chat feeds for nominations for Language of the Month and Learn You a Lang?
CMM: The printable-ascii tag's description says "The solution can only contain the 95 printable ASCII characters", like restricted-source. But most questions it's used on seem to be just challenges related to printable ASCII. Should we change the tag description?
Today my teacher asked me what the connotation of the word "dupe" is. I said, "negative". "Good, but why?" "Well, because a dupe might be closed by the community as a similar question that might already be answered." Teacher frowns. :P
In a fictional 2D world, a set of 2D printing instructions for an object can be represented by a list of integers as follows:
1 4 2 1 1 2 5 3 4
Each number represents the height of the object at that particular point. The above list translates to the following object when printed:
#
# ...
This isn't very widely known, but what we call the Fibonacci sequence, AKA
1, 1, 2, 3, 5, 8, 13, 21, 34...
is actually called the Duonacci sequence. This is because to get the next number, you sum the previous 2 numbers. There is also the Tribonacci sequence,
1, 1, 1, 3, 5, 9, 17, 31, 57, 105, 1...
@xnor They are a weird mix of obvious tiny saves which I don't feel are worth duplicating an answer over and some really well golfed stuff. It's not all that easy.
Hello everyone and welcome to the second-ever Language Design Workshop. The general premise is that y'all can post work you've done or are doing on esolangs and people will give feedback. In short, y'all'll get to show off our languages and their features, chat about them, get feedback, try out WIP languages, and, hopefully get ideas over the next 24 hours.
@ais523 I think ¹ is worth having because it makes debugging much easier. I also often wish Jelly had support for normal brackets because they're so much easier to read and type than $ƊƲ¥ɗʋ (when you've finished, you can convert it to those forms for golfiness, of course)
I was thinking about a language where the only flow-control commands are SKIP NEXT COMMAND IF..., GOTO NEXT OF THIS COMMAND, and GOTO LAST OF THIS COMMAND (as in the one before it).
@pxeger supporting normal brackets would use codepage space and still need some way to assign adicity but it also wouldn't be hard to assign adicity and we are talking about a codepage where ( has no assigned functionality
@mousetail One of my other many projects was gonna be a golfing library for Zsh. It never worked out, mainly because Zsh is such an unendingly inconsistent language that it's hard to think of generalisable library functions (beyond basic aliases for things like echo)
variable width characters would be the next big step in golfing languages, but make them impossible to write (or read) manually so I don't know if they would be a good thing
@Seggan You could definitely save a lot of bytes that way. I'd say it's worthwhile. You can't fundamentally change the language like you can do with macros though
@mousetail One big advantage that the traditional codepages of golfing languages have over more interesting compressed formats is that you can immediately visually inspect byte length based on how wide the code is
I was gonna make an ASCII-compatible translation format for my language's codepage, but then some things would consist of 2 characters but still be encoded as 1 byte, which makes them confusing
A pristine program is a program is a program that does not have any errors itself but will error if you modify it by removing any contiguous substring other than the entire program.
A crystalline program is sort of the opposite. It is a program which doesn't have any errors itself but will error ...
@mousetail i had ideas for this before i knew what i was doing. its a shame that defining the shape of a tree isnt super useful because you can totally do that with a single binary number with an unambiguous ending point :P
the thoguht was to have the number of bits to grab for the next "character" be completely context dependent
so like if you used some command relating to lists that needed to know if you were doing 0 indexed or 1 indexed, the next bit would determine that, and any other args could go right after the bit :P
I worked with a type of compressed assembly for a bit that used that type of encoding, but also there where instructions that modified the tree itself. Impossible to write by hand