vedantnair

This is great feedback. Thank you.

> 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.

Hmm... good point. Would you say that a directory per device is the best way to manage robot config? Have you felt that non-technical users are comfortable with this? Curious what your experience has been like.

> oh! This was a strawman argument to motivate their SAAS. Still, it's a pretty weak one.

I don't think this is a strawman argument. This is a problem we've heard from real robotics teams as they scale their fleets. I did my best not to shill. I'd like to think that reserving one sentence at the end of the blog is acceptable.

Still, I'd love to hear where you think the arguments are weak so I can reconsider them. Thanks again for reading. I appreciate it!

The problem with using Git as the backbone of your robotics config management is that Git is more like a datastore, where you really need a database.

As you scale, this affects your ability to scale RobotOps, to stand up other fleet management tooling, and to provide the security/access controls your customers need.