I don’t know how many times I had to deal with missing VCRUNTIME140.dll or MSVCP140.dll or other crap on Windows. This is not a Linux exclusive problem.
Reading through the comment thread I can’t help but think that your whole situation is self imposed.
Dependency problems are universal and there are tools to deal with it. It just seems that you’re refusing to use those tools (even Windows has winget now instead of relying on every installer bundling / linking its dependencies).
Now, it’s fair to not want to deal with CLI, but your cited experience is an outlier. It is not normal to break your system with just apt update && apt upgrade -y. As a matter of fact apt will not upgrade if there are conflicting dependencies, you sort of have to force it to break your system.
There are wrappers that provide a GUI for apt (and even dpkg, which is usually invoked when double clicking a .deb file) so why not using them?
In Windows dependency issues are often offloaded to the provider of the software, but they are still just as present. In Linux this problem was solved[1] a different way — via package managers. I don’t want to be the “skill issue” guy, but refusing to use the platform intended tool to solve a problem is kind of a “skill issue”. At some point you are responsible for knowing how to use an OS, just as you are responsible for knowing how to drive a car if you want to drive a car.
dependency hell is still an issue so take the word with a grain of salt. ↩︎
This need’s to be higher in the comments!