Hell yes. Why does [established practice] have to mean [best practice]? With all the security concerns and regulation regarding flight, it's easy to imagine ho

Hell yes. Why does [established practice] have to mean [best practice]? With all the security concerns and regulation regarding flight, it's easy to imagine how hard it is to move forward and innovate in usability. I'm not saying upending git for something better would be trivial, but I don't want to constrain my imagination by thinking it's not possible. If you can coherently explain what you need [git replacement] to do, and explain it simpler than you would explain git itself, then you have an outline of a superior tool.