I have both of those installed on multiple systems and I've never needed to mod my .bashrc file.
"Don't even get me started with all the software that doesn't even have an install (those tar.gz ones for example)."
You mean software distributed as source code only? Yes, those can be annoying for the average user, and even the experienced one. But that's entirely on the dev.
"Not sure how does one use a "respiratory"... maybe you meant a repository?"
Yes, I was on mobile.
"Do you actually even understand how apt, yum, zipper et al. actually work? Try installing chrome with apt... or things like Redis-insight. RPM and DPKG are hard??? Now that has to be a joke."
Yes, I do understand how package managers work. I'm guessing you want to make a dig at the fact that under the hood apt and yum (dnf) work with deb and rpm files respectively. The point is that for the most part, a user shouldn't be downloading .deb/rpm files from websites and installing that way. An application should be installed from the distros repository via the package manager. Granted, Chrome doesn't exist on the Debian/Ubuntu repos, and you do need to install the deb file from Google. But this isn't a random application from a random website. And once do you install the Chrome deb, you actually can install Chrome (and Chrome Beta and Chrome Dev) from the repos.
You can even see it gets upgraded with an apt upgrade.
And if you're installing something like RedisInsight then you should know how to install things from outside the repo and understand the risks. 99.9% of everything else you need will be in the repo.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
"Try installing stuff like Rust, Node etc."
I have both of those installed on multiple systems and I've never needed to mod my .bashrc file.
"Don't even get me started with all the software that doesn't even have an install (those tar.gz ones for example)."
You mean software distributed as source code only? Yes, those can be annoying for the average user, and even the experienced one. But that's entirely on the dev.
"Not sure how does one use a "respiratory"... maybe you meant a repository?"
Yes, I was on mobile.
"Do you actually even understand how apt, yum, zipper et al. actually work? Try installing chrome with apt... or things like Redis-insight. RPM and DPKG are hard??? Now that has to be a joke."
Yes, I do understand how package managers work. I'm guessing you want to make a dig at the fact that under the hood apt and yum (dnf) work with deb and rpm files respectively. The point is that for the most part, a user shouldn't be downloading .deb/rpm files from websites and installing that way. An application should be installed from the distros repository via the package manager. Granted, Chrome doesn't exist on the Debian/Ubuntu repos, and you do need to install the deb file from Google. But this isn't a random application from a random website. And once do you install the Chrome deb, you actually can install Chrome (and Chrome Beta and Chrome Dev) from the repos.
Example: dev-to-uploads.s3.amazonaws.com/i/...
You can even see it gets upgraded with an apt upgrade.
And if you're installing something like RedisInsight then you should know how to install things from outside the repo and understand the risks. 99.9% of everything else you need will be in the repo.