I think you can say "that people are arguing about it makes it significantly political".
I don't think you can say "that people are arguing about it makes it a meaningful thing to do".
Why is this so upsetting?
...because I don't want to be paying the externalities (workflow changes, having to keep up with the new "correct" naming) caused by a game of "who can be the most woke" between a vocal minority of progressives
Your second bullet is an argument against this change from the position that it's an unasked for burden. In general, I get that. In the specific context of software engineering, it's a little more surprising. Tools, APIs, interfaces, terminology, etc... are in constant flux. Software has to be actively maintained to be kept functional. Software engineers have to always be learning in order to keep current. A vendor changing something like this is par for the course, right? Why such an extreme reaction?
>A vendor changing something like this is par for the course, right? Why such an extreme reaction?
I'd be similarly pissed off if an upstream API provider suddenly decided to change all their identifier names for stylistic purposes. eg. the CTO woke up one day and decided that all of their API endpoints should be changed from camel case to snake case.