On the obsessive statelessness of Peril

Thanks for the clarification. I read the title as "On the obsessive statelessness of Perl", and thought, in order, "cool, an article on HN about Perl!" and then "wait, Perl is about as far from obsessively stateless as possible."

I dislike articles that do this, but this post explains what it is at the very beginning:

> To get you up to speed on Peril, Peril is a tool that takes GitHub webhooks, and makes it easy to build one-off actions. It does this by having a per-account settings JSON, that connects JavaScript files to events from webhooks. So, for example, you can write a rule which runs when closing an issue in GitHub that looks for associated Jira tickets and resolves them. Peril provides no implicit actions like that, it instead offers a JavaScript runtime environment optimised to this domain so you can make actions to fit your needs. Like a collection of single-file probots.