Define project goals

When I first introduced bisectable, my goal was to create cool useful tools. At the time, bisectable was written in perl 5.

Since then I've been making decisions that are entirely opposite of creating useful stuff. Most significantly, the whole code base was rewritten in 6lang. Although I can write stuff in 6lang faster, it requires huge amounts of effort to hunt for bugs in rakudo itself. This turned the whole development process into some kind of a pleasant nightmare. Then, we have Quotable using 6lang regexes to grep millions of lines, Benchable using svg-plot to graph things, sake instead of make… all of this stuff and all other dependencies take small bites of my time (for bug reporting, maintenance and a little bit of fixing from my side also).

So, if we ever have to decide whether something is needed or not, here's the idea: “Whateverable – turning rakudo into a practical tool”. Or something like that. In other words, let's accept that what happens in this repo is mainly not about the development of tools, but about making rakudo useful.

It may sound a bit sad, but on the other hand, by doing so we can make sure that these bots are the first line of fire when something bad happens in rakudo.

Read the linked IRC discussion, the Sakefile, and the dependency information referenced in the issue to understand the project's current direction and maintenance costs. Done means reaching agreement on explicit project goals and recording a clear principle for deciding which work belongs in whateverable.