Nope, try again.
> They are not classes, and the objects they instantiate are not objects.
They are classes, and the objects that are instances of them are objects. In fact, they are often the best objects -- by SOLID standards -- as their names tend to hint: their names reflect their role as agents directed at a single purpose -- that is, that they adhere to the Single Responsibility Principle.
> The main argument against this "-er" suffix is that "when you need a manager, it's often a sign that the managed are just plain old data structures and that the manager is the smart procedure doing the real work".
"Manager" in particular is a name that signals trouble, because "manage" is a vague term under which multiple different, poorly connected responsibilities are often lumped.
> When you add the "-er" suffix to your class name, you're immediately turning it into a dumb imperative executor of your will. You do not allow it to think and improvise. You expect it to do exactly what you want — sort, manage, control, print, write, combine, concatenate, etc.
You may have a coherent point here, but its hidden under some really bad anthropomorphizing metaphor -- obviously, unless I'm designing fancy-pants AI code, I don't what my code -- classes or otherwise -- to think, improvise, or in any other way do anything other than do exactly what I want. So portraying it not doing any of those unwanted things as a reason not to engage in a practice is, well, not convincing.
This entire article suffers from:
1) A lack of concrete definition of the problem is,
2) A lack of concrete examples of the problem that demonstrate that, indeed, it is a problem, and
3) A recommendation (with examples) of what would be good to do instead of the problem.