And?
There is a big difference between being resigned to doing more work as necessary and defending the need to do (what should be) unnecessary work.
I feel like you’re trying to make a semantic argument here, but…
remove v.
- take (something) away or off from the position occupied.
They will take away chat commands from chat. - eliminate or get rid of.
They will eliminate that functionality from chat.
That is irrelevant, has never been the case, and likely never will be. In this case, Twitch will continue to maintain access to the chat commands from the website and won’t be using “common” APIs to do it.
There is a difference between adding features and removing functionality. I can add support for new features when and if I feel like it. In that case, that feature just won’t be available for a while. In this case, basic functionality will be broken.
I said it’s better to be reactive. If you have no reason to believe you are not a moderator, then you might as well proceed as though you are one, and adapt as warranted. I didn’t write demize’s code, and I don’t dictate the right way to do things.
That doesn’t mean I can’t complain when breaking changes are made, and moreso when the justification is illogical. It’ll somehow enable new chat features, make things more consistent, and more convenient. There’s some serious doublespeak going on here.