oh I've been down the "I can just fix macOS" road. The sooner you move away the better. so much time wasted on plugins like these.
you effort will just be null the second apple change the usability apis enabling hammerspoon, like they did countless times before. I don't even rename the name of the fallen apps before it.
instead now I contribute things as long lived proper features on KDE and hopefully advance humanity instead of apple profits.
You don't think that the banks aren't going to be passing along the burden of the FDIC special assessment to customers, do you? That's not at all how finance tends to work.
Or you can specify a git commit, or a path if you want to alter it locally.
> No way to keep track of what to change when mix create outputs something different next year.
`mix.lock` keeps track of your resolved dependencies and should be checked in along with your code. Mix/Hex can also be provided the exact `==` versions rather than the `~>` or other Version specifiers
What did you feel you needed to change on your project because the default template had changed? If the code works, then it keeps working.
I've run into this with the Phoenix generators a bit because you need to make changes to your project if you want to update to newer versions of the Phoenix libraries, but they produce documentation about what you need to change.
See, I feel it's a way to have some 'frameworky' elements in my projects that are wonderfully standardized. the changes that do occur usually are worth it.
If anything I sometimes find myself annoyed that Ecto is not there by default, because it's part of almost all my projects, and often even a one-file script might benefit from bits of it.
