re: Is git the be all and end all of version control? VIEW POST

FULL DISCUSSION
 

I think Git is simple enough to create tools over it (like Github) in order to extend it.

Example: Pull Requests aren't a feature of Git, but nobody would use a version control platform (Github, Gitlab, etc.) without that feature which was built upon Git branches.

So instead of doing Git again from the ground I think is better to just improve tools built upon Git, maybe simplify the flow to avoid messing it up.

 

That's reasonable. Git could be a bit like the assembly language for version control. Regardless of abstractions you build, it compiles to git for compatibility and leverage the immense work put into it.

 
 

I really like the analogy of git as the 'assembly language' for version control.

From a quantitative developer perspective (ML, AI, and data science), one of the biggest issues with managing version control with conventional repo platforms (GitHub, Bitbucket, etc) is that they track code properly, but not other mission-critical development properties that currently need to be managed manually (package/lang versions, model configuration).

While something could be built on top of one of these platforms to augment the features that already exist, we see going straight to git itself to be the best solution for building a more all-encompassing tracking system that works for developers in our domain.

Would love to hear more perspectives from people in the machine learning, data science, and artificial intelligence spaces, as my company Datmo, is building a CLI tool and web platform that tries to solve these issues!

code of conduct - report abuse