I started reading his sympathetically, I am very familiar with this problem.
> The first is a directory per device in a single repo. It is admittedly the most intuitive layout, but every config change across every device lands in the same commit log. At 100 devices, that history is unreadable. If you want to see what changed for one device, you’ll find yourself wading through hundreds of unrelated commits. Git wasn't built to filter history this way.
Wow, these people don't know how to filter git log by directory? This is pretty messed up, no wonder that git does not work to them.
> This is why we built Miru, config management for scaling robotics teams.
oh! This was a strawman argument to motivate their SAAS. Still, it's a pretty weak one.
> The first is a directory per device in a single repo. It is admittedly the most intuitive layout, but every config change across every device lands in the same commit log. At 100 devices, that history is unreadable. If you want to see what changed for one device, you’ll find yourself wading through hundreds of unrelated commits. Git wasn't built to filter history this way.
Wow, these people don't know how to filter git log by directory? This is pretty messed up, no wonder that git does not work to them.
> This is why we built Miru, config management for scaling robotics teams.
oh! This was a strawman argument to motivate their SAAS. Still, it's a pretty weak one.