When I maintain a gem with a name that implies simplicity and security
I want to make clear that the simplicity of the gem sometimes means additional work to do for the developers using it
So that people don't miss important considerations
And have the best chance of assessing risks adequately
And to use the gem for what it's good at
When I maintain a gem with a name that implies simplicity and security I want to make clear that the simplicity of the gem sometimes means additional work to do for the developers using it So that people don't miss important considerations And have the best chance of assessing risks adequately And to use the gem for what it's good at