Sean Halle

Branches for various levels of complexity

We were talking about also having branches that add more advanced features. Actually simplify the main branch, strip things out. Then add other branches, the ratchet up the complexity.

For example, add caches in a different branch, and add multi-core in a different branch. Right.. we actually discussed a system of branches. What do you think about possibly choosing names for the branches that are descriptive of the goal of the branch?

Vision of "commented" branch in Sodor repository

Kritik created a separate branch, that add verbose comments to the code

The important thing will be making this obvious and advertising its existence to everyone, so that beginners don't struggle, and then later discover a commented version exists.

Also, it will be important to make it quick and easy to switch between the two. And it will be important to make it easy to keep the two in sync.

I'm thinking that in practice, people will jump back and forth often.. at first most time in commented version.. then gradually spend more time in non-commmented version..

As spend more time in non-commented, they will start jumping -- hit a place where they don't understand, jump over to commented version, then jump back.