This sounds like a nice opportunity to climb on the native widget soap box for a moment. I am not at all convinced that native widgets would make us faster (though they might help with specific things, e.g. rendering large blocks of text), but they would force discipline on us. Imagine the cruft that would disappear if the windowing system were *completely* replaced. That is, of course, more easily said than done, and a lot of code depends on the cruft. You did say you wanted to start a discussion :) Bill ________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] on behalf of Sean P. DeNigris [sean@clipperadams.com] Sent: Wednesday, November 23, 2011 2:20 PM To: pharo-project@lists.gforge.inria.fr Subject: [Pharo-project] Backward Compatibility The Pharo Manifesto (http://code.google.com/p/pharo/) lists "Not backward compatible" as one of its 4 tenants. Yet, while working through the issue tracker, I've noticed some adding/keeping complexity to keep things backward compatible - most recently http://code.google.com/p/pharo/issues/detail?id=5007. I just wanted to start a discussion because obviously the more mature Pharo gets, the harder it will be to remove things... Sean -- View this message in context: http://forum.world.st/Backward-Compatibility-tp4101111p4101111.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.