If my goal is to make my computer work for ME, then I want my development system to maximize my leverage and minimize my effort. Breaking compatibility for cleaner code subverts this, as Hannes said,
>> Constant input in maintenance effort is needed. I want to use my time applying Smalltalk to real-world problems, not API changes. A blue-plane innovation is worth breaking backward compatibility, reinventing the past isn't. >> maintaining libraries and maybe compatibility layers are very welcome. >> > Yes, and how did we ever thought we could invent the future with Squeak > when in reality, we could not even change a typo in a comment? > > Marcus > > > >
