Comment #9 on issue 3817 by camillob...@gmail.com: make Object >> error: deprecated http://code.google.com/p/pharo/issues/detail?id=3817 Just to give an example of what I mean. In Java the general error handling is mainly based on a set of specific classes, the generic Exception is almost never used. For instance InvalidArgumentException is a common use-case where in the existing Smalltalk code `self error` is used, whereas a specific would be appropriate. In many places like BlockContext >> valueError generic errors are thrown with only a user readable warning. So the main issue here is, that in may places a specific error could be used, but it isn't and hence a specific treatment of said error makes no sense at thus is not used (this is what I called a broken design). Of course the whole system has moved towards the usage of generic errors, but this is the same as starting to use generic dictionaries instead of proper objects, just because it is less effort to do so. Besides work on adapting all the senders of `Object >> error:` what would be other negative effects?