The main reason is because, while Pharo is obviously heavily inspired by (and, in fact, a fork of) Smalltalk, it&#x27;s not trying to stay Smalltalk-80 compatible. Think of Racket: Racket started life as DrScheme, but as the goals of Racket gradually drifted away from being &quot;just&quot; a Scheme dialect, they decided to just call the entire language Racket to avoid confusion.<p>Pharo&#x27;s doing the same thing. For the moment, the changes are relatively minor--new GUI hierarchy, support for method lambdas, some cleanup of the class hierarchy, support for traits alongside classes, and so on--but the team wants the flexibility to break compatibility more thoroughly as time goes on.<p>In other words, it&#x27;s not about Pharo not wanting to give credit where it&#x27;s due, but rather about not setting false expectations.