3 ms·
Its not the rate of change that is the problem. Its the quality of the changes and the way they are being implemented. In all of your examples you keep mention
by muskmusk 5y ago
Its not the rate of change that is the problem. Its the quality of the changes and the way they are being implemented.
In all of your examples you keep mentioning that they either remove or change something you like thus forcing you to do something to keep up. That is the real problem, they are making changes that the user is forced to deal with. If all of these changes were fixing things you were legitimately annoyed with then you would be a happy camper, but that doesn't seem to be the case.
- sixothree 5y ago100% agreed. Whenever a feature is moved or changed, you can almost certainly assume it's going to be broken as well.