So... Let me get this straight... Everyone is all wound up because the fee's have changed...
If you actually read you understand but you are clueless, so I take pitty on you.
I did, I read the
code the only real change in the behavior is it's checking a run time variable vs a constant.. and said run time variable is different then the constant, if one wants the old behavior pass old value to new run time variable. Or if really concerned write a patch that changes that magic number back to the old magic number and put in a pull request.
It also calculates the threshold where a transaction can't be spent without costing so much in fees that it's not worth spending. This is derived at runtime from the values you quoted.
And if such a "dust" transaction comes through the p2p network, it ignores it. If a miner mines it, then so be it, but the node itself won't contribute to propagation of the dust spam.
Miners can set this threshold at runtime easily instead of having it compiled in.