Comment #3 on issue 3436 by sebastianconcept: #copyFrom: is broken http://code.google.com/p/pharo/issues/detail?id=3436 I don't get it. When you take any non squeak based smalltalk you'll see that #copyFrom: is consistent and intuitive. When you take Pharo you get that: 1. it's broken even for smalltalkers (imagine random citizens) 2. is manipulating (admitedly) dangerously (check implementor comment) 3. is doing something extremely primitive without using the prefix basic (or whatever that suggest that this is a thing to use unless you know what you're doing) 4. our community response is that reporting this is invalid? Can we please fix this instead of rationalize? Suggestion: a rename of the current Object>>copyFrom: will be enough. How to rename it? with something that suggest is going to manipulate the freaking instance variables) there is code depending on that? screw it. If they started with the wrong foot, they should pay the price of their upgrade (they are guilty of creating a dependence on something broken).