It's more functional than object-oriented and I read the former better than the latter. 😅
KaKi87
You understand perfectly.
How is the manual step more secure though ?
What does the user do before downloading a DEB that makes that gap between manual and automated ?
I'd be willing to try and reproduce that, but I don't see anything.
My point is that I'm working a solution for end users.
The solutions you're offering are not user-friendly.
I don't care.
I'm and end user working for end users.
My main use case is end user desktops.
Which isn't user-friendly.
Well, I'm just automating what people currently have to do manually : visit GitHub and download DEB and install DEB.
If the automated process would be dangerous then the manual process also would be, and that would be on the maintainer for not providing an APT repository or a Flatpak, not on the user for just downloading from GitHub.
Why the OOP structure and syntax ? Sorry but it makes it difficult to read for me even in my own language 😅
You said automation breeds laziness (by design, to an extent) and lazy end users tend to shoot themselves in the foot.
So, my question is : what part of automating download of DEBs from a specific source can be shooting oneself in the foot compared to doing the same thing manually every time ?
The MIT license will take care of that.
Also, to force the user to accept and acknowledge that the software they are installing using this tool is not verified to be safe is inducing fear and/or guilt, therefore is bad UX, I'm not doing that.