I worked using VA-Smalltalk and Envy for 3 years. One interesting thing about Envy, is that all the versioning model was available as objects that you can mani

I worked using VA-Smalltalk and Envy for 3 years. One interesting thing about Envy, is that all the versioning model was available as objects that you can manipulate, and versioning was not file based but per module/class/method. In our team each developer worked on a branch, we developed an in-house tool to automatically merge all the branches. Having the class model available made easy to identify conflicts and class shape changes. The tool resolved most of the cases and also created the migration script for the object database (GemStone). Nowadays I'm working with JavaScript, using VSCode, webpack, and a long list of tools... it feels like something went wrong in the dev tooling evolution.