4 ms·
> This amounts to saying that we should accept codebases continuing to contain exploitable vulnerabilities indefinitely. Right, why shouldn't we? I have a CLI
by volta83 5y ago
> This amounts to saying that we should accept codebases continuing to contain exploitable vulnerabilities indefinitely.
Right, why shouldn't we?
I have a CLI application for storing TODOs. It never accesses the network, I don't really care if it crashes, it does not have an expiry daye.
I have a constant amount of time to work on it. To me it is more value to put that time into new features that save me a couple of seconds here and there as a daily user, than to put all the time allocated for months or a year of working on the app to re-write it in a different language to remove the occasional monthly crash I don't care about.
For me, the decision is a no brainer: my time is better spent in the stuff that adds more value, and "avoiding exploitable vulnerabilities" is not it.
I suppose that this is the situation for many apps.
You are claiming that this is wrong. Prove your claim.
- lmm 5y agoIf it's a personal app that you're not going to share with others then that app does have a finite expiry, admittedly in a slightly morbid way. I'd submit that an app with a truly stable userbase requires an impossible level of fine tuning - in reality an app is either growing or shrinking.