For a programmer sitting in front of a desktop that already has Linux on it, following those instructions would take less than five minutes. Easy.
For a typical Android user, they wouldn't know what they were looking at even if they had a Linux machine, which they don't. And would then get turned around by a simple typo like "apt-get-install" instead of "apt-get install" if they even make the attempt.
But because it's already "easy" for the people with the expertise to make it easier, the only people who could solve the problem are the people not experiencing it.
> the only people who could solve the problem are the people not experiencing it.
Its more that companies provide some hard to use escape hatch for their anti features which silences all criticism "You just run this command" while still keeping it out of the hands of the normal user. The problem has already been solved, you don't have to run abd to remove apps on android, unless the app is specifically preventing you from using this feature.
Sometimes the scripts on xda-developers come bundled with an older adb version specifically because they don't expect people to know how to install it themselves.
Although, on a second thought if a user then decides to run the `debloat-google.sh` without knowing what he does the user might end up quite frustrated as a result. So I guess you're right.
I think google has been gradually restricting what adb is able to do.
For a programmer sitting in front of a desktop that already has Linux on it, following those instructions would take less than five minutes. Easy.
For a typical Android user, they wouldn't know what they were looking at even if they had a Linux machine, which they don't. And would then get turned around by a simple typo like "apt-get-install" instead of "apt-get install" if they even make the attempt.
But because it's already "easy" for the people with the expertise to make it easier, the only people who could solve the problem are the people not experiencing it.