Hacker News Reader

Comment by pkphilip | Hacker News Reader

The primary challenge with Pharo is the complexity of using this in a multi-user type of environment where the image is shared between people. How does one do that?

View on HN

I did commercial team Smalltalk development using the Digitalk toolset, for a team of around 16 people.

You start with a base development image, loaded with the toolset and frameworks for the project. No one modifies this image.

You share the app code through a source control tool. We used Team/V. Start up the project base image, open the repository browser, load the project packages. Make changes, commit source back to the repository. No saving of the image for development.

So shared, but never changed base image for the project, and app code sharing through the source control repository.

Pharo source management is based on Git, so the workflow is not special. We build the development images on the CI so every developer can download the already prepared image with the latest commits, but that is just for convenience.

Though there is the issue of: the changes in your image are not necessarily the changes in your local repository and the syncing of both can sometimes cause annoying issues. In most cases I've learned to work around it, but it wasn't plug and play straighforward.

Note the Cuis-Smalltalk Daily Workflow:

https://cuis-smalltalk.github.io/TheCuisBook/Daily-Workflow....

Reply on news.ycombinator.com