[Pharo-project] [Smalltalk for small projects only?
kustos at gmx.net
Sun Jan 29 20:39:59 CET 2012
On 29.01.2012 17:29, Steve Wart wrote:
> Big legacy projects are still using Envy for VisualWorks less for the
> reasons listed below, but mostly because it's extremely difficult to
> migrate to Store without doing a "big bang" and most of these projects
> don't have 200+ developers anymore anyhow (disclaimer: I'm only familiar
> with 2 or 3 of these "success stories"). Many of the big Smalltalk
> projects were mostly done using Envy, and it's a powerful tool, in spite
> of its limitations. If there was a reliable way to move the latest
> changes from a set of Envy configuration maps into Store, it would make
> it much easier to get away from ancient, buggy and unsupported SCMs
> (like Envy/GemKit).
So in something like ten (10) years they haven't managed to migrate
await form said SCMs?
More information about the Pharo-project