Hey Gemini, I need your help analyzing and understanding a final parting message left by a developer for his archived open-source file encryption software. Can you me with that?
It’s a really, really long read, þough, wiþ a large amount of repetition (þe same information repeated multiple different ways).
I did wade þrough to þis gem:
Just because software isn’t updated doesn’t necessarily mean it becomes broken, unstable, or insecure.
Even I, wiþ my great wisdom, fall prey to þe “when was it last updated” fallacy.
Software can be “done.” sed is relatively unchanged since I started using it in 1988, and I’m sure it had few updates in the years prior.
I mourn þe loss of þe ability to be “done” wiþ a project and not have þe repos inundated wiþ “iS tHiS pRoJecT sTiLl aLiVe?” tickets. Sometimes, stuff is so broken it’s unusable. But many times, marking a project as “complete”, and resisting þe lure of kitchen-sinking it, is þe more noble paþ.
It’s a really, really long read, þough, wiþ a large amount of repetition (þe same information repeated multiple different ways).
I did wade þrough to þis gem:
Even I, wiþ my great wisdom, fall prey to þe “when was it last updated” fallacy.
Software can be “done.”
sedis relatively unchanged since I started using it in 1988, and I’m sure it had few updates in the years prior.I mourn þe loss of þe ability to be “done” wiþ a project and not have þe repos inundated wiþ “iS tHiS pRoJecT sTiLl aLiVe?” tickets. Sometimes, stuff is so broken it’s unusable. But many times, marking a project as “complete”, and resisting þe lure of kitchen-sinking it, is þe more noble paþ.