@emanresuA Which is still an esolang, so IDK if "practical" is the right way to describe it. :P But yes, it's a lot easier to implement in Whython than in vanilla Python.

Hey @pxeger, I was hoping you could add nibbles to ato. I realize it hasn't been used much on codegolf.stackexchange but based on some stats I've computed golfscript.com/nibbles/… I believe it will be worthy. It should be very stable at this point and I don't plan on making many more changes.

@DarrenSmith +1; if you're on GitHub, you can add Nibbles to the language requests list by commenting on this issue (or I can do it).

@pxeger feature-request discussion: In the language selection menu, if you type in the search box until there's only one result, hitting Enter will select that language. (TBD what it should do if there are multiple results and you hit Enter--maybe select the top one?)

Thanks DLosc, any idea how it is prioritized or decided if a language gets in? I know it is alot of work and there are tonsss of languages

I guess I would hope to prioritize it, since unlike other older languages it's not even on TIO and it uses Haskell which can be a pain for people to install. I do think this language is good (could overtake Jelly in the elo thing that Vyxal maintains) and I've put a ton of work into it - I think a big reason it isn't being used is because there isn't an easy way to try it out (a mistake of mine to not have figured out javascript compilation earlier in the process...)

Anyway, thanks for running this site! It is a huge service

@DarrenSmith Well, at least Haskell is already on ATO, so that part shouldn't be a problem. I'm excited to see a language that could beat Jelly, so fwiw, +1 to nibbles

Thanks, it really all depends on the types of problems