-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vigil++ It's Vigil for C++ but with the chance of redemption! #28
Comments
Isn't the lack of redemption half of Vigil's gimmick, though? |
You have done well to recognize the rampant deceit and corruption present in modern software, but in your current state you lack the courage to do what is necessary to correct it. Take care, for those who tolerate the existence of evil become evil themselves. |
I wish no schism and much here is true and the ways of the snake may well deserve their code base burned but I can not correct that which is ashes so surely the |
Vigil does offer a path for redemption for code authors (see issue #24). This is ultimately left to the discretion of maintainers, because Vigil seeks to be relevant to a wide array of diverse coding cultures, some of which have not yet awakened to the benefits of capital punishment. Where Vigil takes a hard stance is on the code itself, because unless evil functions are completely purged they will infect and dirty other code. This is perhaps the most important cornerstone of Vigil (see the FAQ's position on code that calls into corrupt functions). A single fly can spoil the ointment, so Vigil automatically minimizes the amount of time your code spends in a tainted state. A function that renegades on its promises is highly likely to have other, more subtle bugs. By deleting the code outright, Vigil gives you the opportunity to rewrite the function properly from scratch, undistracted by your previous mistakes. Bear in mind that if an author is truly redeemed, their desire will be to fully reject the old way of life; to cast it aside and burn it so that they have no temptation to return. I know it seems harsh, but if your corrupt functions weren't deleted, they would continue to be a thorn in your side. It's purely for your own good that we do this. |
Epiphany! I recant the ways of redemption - that which is wrong must be punished. The codebase must be cleansed, capital punishment is the only route to true redemption I see that now... |
@munificent
https://bitbucket.org/ifknot/vigil/overview
The text was updated successfully, but these errors were encountered: