News for hackers. Stuff that matters.
Re:A New Era for Mechanical CAD by krapht on Tuesday June 15, 2021 @02:08PM (#27519219)
Even if you had that representation, resolving merge conflicts would be a huge headache. Imagine resolving code conflicts by resolving things at the AST level.

Forget CAD, we don't even have a good way to version control images, something programmers work with every day, besides "use Git LFS and pretend an image is just a pointer".

edit: just saw GumTree mentioned above. Guess I have something to check out...

Re:A New Era for Mechanical CAD by ofrzeta on Tuesday June 15, 2021 @02:10PM (#27519256)
Of course not possible with images as a binary blob but it could be possible with a series of operations on a (vector) image ("event log").
Re:A New Era for Mechanical CAD by dTal on Tuesday June 15, 2021 @04:16PM (#27520924)
>Imagine resolving code conflicts by resolving things at the AST level.

This sounds extremely nice actually. The more semantically aware the version control system is, the more likely it can gracefully handle merge conflicts. A textual diff is a very low level transformation primitive; composing them doesn't guarantee very much at the higher level.