jellylanguage VS perlweeklychallenge-club

At least on the Code Golf Stack Exchange, I see a lot of people using esolangs for golfing (two random examples: Jelly [1] and O5AB1E [2]). I expect that it could be a line or two shorter at least with a change of language. As I recall some of the golfing langs also have pretty sophisticated compression techniques for strings, although they might be optimized for dictionary words. Careful distinction: they are all optimizing for bytes used, not characters used.

I don't want to neglect your shameless plug, but I struggle enough to find a solution to some of the puzzles I wrote (hence the undo), so finding the shortest path is a little daunting.

[1] https://github.com/DennisMitchell/jellylanguage

[2] https://github.com/Adriandmen/05AB1E

ADDITIONAL COMMENTS: I am also solving most of these problems in Jelly, a recreational language designed for code-golf. They are in the same repository under the jelly folder.

Jelly (put the input in the first command line argument):

Yes it is totally possible, Batch script is Turing complete afterall. Since you found Python tutorials, you can just apply the same concepts in Batch. The difficulty depends on the complexity of the language you're trying to make. I would recommend trying to make a stack-based language first, with the syntax similar to golfing languages (ie, one character is one "command", check out https://github.com/DennisMitchell/jellylanguage), since that would be the easiest. But obviously if you're up to it you could make a fully fledged programming language.

This is a basic version of many commonly used ideas for string compression in golfing languages. Jelly [0] is a good example of a more practical and versatile approach that builds on ideas such as this.

[0] https://github.com/DennisMitchell/jellylanguage/wiki/Tutoria...

(As an aside, some people "stop" here and then make programming languages based on this - because that is a simple interpreter... you could write a compiler for this language, or extend it - and the great golfing languages take that starting spot and keep going - don't worry about trying to replicate it, it takes some insanity to go that far - the point is that a stack based language is the starting spot for some impressive systems... like the JVM itself)

If you like code to be as short and unreadable as possible, try out Jelly.

Arguably, however, if you think about "High Level" in terms of "how many keystrokes do you need to do X complex task" (kinda like some mean komolgorov complexity measure over a set of tasks) then code golf languages could probably be the most "high level". Take Jelly for instance. Incomprehensible garbage when written, but goddamn if it isn't character efficient.

I am waiting for a time when we get Angular or React in Jelly [1]

[1] https://github.com/DennisMitchell/jellylanguage/wiki/Tutoria...

Being honest with naming things is also a great roundabout way to ensure you write maintainable, readable code. If the name is honest and it feels awkward, it's a good red flag that there might be a problem with the approach you're taking. I think code golf languages (a-la [0]) are a good example of this approach as well, when your language is as terse as possible, giving very deep consideration to what the language actually does is crucial.

[0] https://github.com/DennisMitchell/jellylanguage/wiki/Atoms

Each week Mohammad S. Anwar sends out The Weekly Challenge, a chance for all of us to come up with solutions to two weekly tasks. My solutions are written in Python first, and then converted to Perl. It's a great way for us all to practice some coding.

In the previous edition Mohammad sent a call to get sponsor for his Weekly programming challenge. Several people replied to me. Those messages were forwarded to Mohammad as that is his gig. However, I noticed that the link we used to have at the top of the Perl Weekly was only showing up on the web site. I added it back. In a nutshell, if you'd like to spoonsor/financially help the work of Mohammad S Anwar then either contact him or just support him via Patreon. If you'd like to support my work then you can do so either via Patreon or via GitHub.

I run The Weekly Challenge project primarily focus on Perl and Raku but open to all programming languages. It was started on 25th March 2019. It has been going on un-interrupted ever since, thanks to the strong 350+ members of Team PWC. We were lucky enough to have solo sponsor, Perl Careers run by Peter Sergeant since July 2019 without break. Initially we had weekly prize sponsorship but later it was changed to monthly sponsorship. The best part was, I didn't have to move a finger to find the sponsor. Pete was generous enough to come forward and continued supporting the project for such a long time.

Challenge, My solutions

I am not sure, if you noticed this but Perl Mongers certificate expired few days ago. I only noticed as one of the contributor to The Weekly Challenge shared link to the site. The very next day, I saw post by Olaf Alders on Twitter talking about it and sharing the tool that can help avoid such incident in future. The certificate has now been restored.

Oh yes, Bruce Gray was a major influence for me as well a couple of years ago. He often participates in the "Raku Study Group" meetings as well - these are very broad and informal meetings every second Sunday but around the end, Bruce almost always brings up some Raku (sometimes Perl) solutions for the weekly challenges from https://theweeklychallenge.org/. In case you are interested, the repo of the meetups: https://github.com/doomvox/raku-study

Back to the topic. I picked up Raku a couple of years ago and I mostly use it as a better shell.

The pros are that you can really quickly and swiftly deliver CLI automation tools and scripts; the language has a unique but very practical regex syntax, you have very rich tools for string manipulation and you have good utilities to "drain CPU" if you are willing to spend more resources to make something faster (e.g easy multithreading for operations). Also, the language is very pleasant to use, it makes you feel very clever and powerful.

The cons cannot be neglected, however, the biggest problem probably being the performance and stability of the only actually working compiler, Rakudo, and its most functioning bytecode VM, MoarVM. The rich string-processing system and regex engine can be surprisingly slothful if you have vast amounts of text, same for precise bigint and rational computations (which are the default). Not many people understand Rakudo (and especially the VMs) enough to work on bugs or performance improvements, and there are not many low-hanging fruit remaining. Considering this, I'm sad that there has been little strategy regarding getting new maintainers, or having a release strategy besides "we will not change anything that might break code, and just release new compiler versions every couple of months".

Also, I don't know how much this is a con for you but Raku is not a language you can just "learn", you have to explore it and always be ready for a new journey. It's a horizontally huge language with a lot of corner cases you probably cannot all keep in mind. I think I'm managing pretty well but it is definitely a risk; you should probably either find a small subset you are comfortable working with and stick to it, or be okay with exploration using whatever goes, from asking others and reading the docs to investigating the core library inside Rakudo (which is not as bad as it may sound but not everybody wants to do).

Each week Mohammad S. Anwar sends out The Weekly Challenge, a chance for all of us to come up with solutions to two weekly tasks. My solutions are written in Python first, and then converted to Perl. It's a great way for us all to practice some coding.

I had almost forgot about participating The Perl and Raku Conference 2023 because of what I have gone through in the last few weeks and still going on. But the best part is, I have booked everything from air ticket to hotel reservations. Having said, I still have to get the slides ready for the my talk about The Weekly Challenge. If you are planning to attend the conference then please do come and see me. I would love to meet as many Perl enthusiasts as I can. I am mostly looking forward to meet the weekly challenge members. I got exactly 2 weeks time to get everything sorted before it is too late.

It's been a very long time that I've made a post that wasn't related to The Weekly Challenge, but it's about time I did :)