Hacker News Reader

A pie chart of the Vigil development time would show something like:

25% Writing code 10% Reading the traceback documentation 40% Writing the README 20% Browsing a thesaurus for the best words 5% Cursing after Vigil deleted part of the example

I tell you what, trying to get this thing to self-host is... tricky.

There is nothing morally upright about begging, cajoling, pleading or grovelling.

Imploring isn't really right either, because it seems too subservient to enforce a requirement on calling code.

It's more like the feudal lords obligation to his vassal - that he provide them with the use of the fief and protect them from others. If the function is the fief, then you provide the use of it only to those other functions that will swear fealty to you.

Rebel, don't forget rebel; a keyword to use an exploit in the vigil compiler to remove it from the hard drive just after escaping to a python environment where it is compiled under less oppressive rules.