Every time I see DVC mentioned I always feel like the idea was so close (and perhaps right in intuition to use git for everything) but the execution had just enough friction that I looked elsewhere. Small DX improvements really do cascade pretty far.
Also I always thought the idea of using Git branches to track experiments was a bad idea. I would never want to only have one experiment "active" at a time. Even if I'm only running one process at a time, I still want to be able to look at outputs and such all side-by-side. Maybe there's some magic tooling they created that makes it workable.
But for a data project it would be a big pain to have separate worktrees just to work around what IMO is a usage anti-pattern to begin with!
[1] https://iterative.ai/blog/experiment-refs
[2] https://marketplace.visualstudio.com/items?itemName=Iterativ...
I'll have to take a look at this. Most/all of my projects use small or medium scale data, and I consider DVC indispensable for tracking data therein. I wouldn't mind having a good system for tracking experiment results, although admittedly I find that a spreadsheet or text file does a pretty good job for what I need to do.
It's neat for research as it stores the data on scientific data repositories like Zenodo and you get DOIs.