jozep
Your comment is disingenuous because you asked if one would prefer if others were carnivorous or vegetarian. This is nonsense because you don’t get to chose what other peoples eating habits.
When you make food for people you ask them what they eat before you serve them something they cannot or don’t want to eat.
I agree with you but one has to acknowledge the proficiency of the US Army. The sheer amount of equipment they have coupled to the good training and 1st class logistics makes it a force the Russian army would not be able to recon with.
Shit the Afghanistan war cost them $300 million per DAY for 20 years. No one else can do imperialism as good as the US Army.
I never said supporting Israel is wrong. I just wanted to respond to your sentence saying that tech company should not be evaluated on their politics. I do not believe this, I think tech company should absolutely be evaluated on their political decisions. Like it has been the case with NSO Group.
Boycotting on technological or political ground is the same. It’s all morality based.
You can say that HP handling of customer service or technological choices are not moral and thus grant a boycott. Some people might think that their political decisions are not moral.
I don’t think you can evaluate a tech company only on its technology. For example NSO Group wrote Pegasus which is a good working spying software. Is their tech doing its job? Yes. Did they sell it to dictatorships enabling the wrongful emprisonment of many people? Seems like it.
Custom configs is for people who might not want to tinker as much so maybe it’s not for you if you prefer Arch.
To answer the question you asked previously, yes I had issues with custom configs from Debian. One I remember is mupdf being launched by a bash script and thus not understanding why did I have two PIDs (one for bash, one for the mupdf binary) when starting.
For context this was important because I needed to know the PID of mupdf to send a SIGHUP to update the view.
Arch also does its own packaging on its repos.
However you are right that Arch tries to stay as close as possible to the source. This is fondamentally different than the debian (and thus all debian-derived distros) way of packaging where they aim for a fully integrated OS at the expense of applying their own patches to many packages.
The patches can sometimes bring issues since they can bring unexpected behaviour if you come from Arch and sometimes will help the end user tremendously since they won’t have to configure every piece of software to work on their computer.
This is really two way of looking at the issue: Arch is make your own OS and Debian has a more hands off approach.