[squeak-dev] when to start trimming?
asqueaker at gmail.com
Sun Jul 22 18:41:58 UTC 2012
> Having said that, we _should_ start a conversation around what will
> become Squeak 4.4.
> I'd like to see a greater emphasis on modularity, myself: if not
> having Environments in the base image now, then at least identifying
> the worst entanglements and working on cutting those. And tests.
> Tests, tests, tests. The tools especially need some kind of framework
> within which to test. A mock environment permitting one to test lovely
> things like #removeClass would be fantastic. (There are building
> blocks all over the place, but nothing assembled in the base image.)
Another thing which might be low-hanging fruit for the next version is
simply cutting out some of our deprecated stuff.
- Removing old methods sending isThisEverCalled.
- the 311Deprecated and 39Deprecated packages?
- unloadability of some of the packages
More information about the Squeak-dev