Yes, it really is true. The XML is not a "completely different language". It is an alternative (but 1:1) representation of the internal Snap code.
There's no absolutely reason why the Snap UI couldn't be feeding the XML to a version control system behind the scenes, and recovering previous versions from that system at will.
> Yes, it really is true. The XML is not a "completely different language". It is an alternative (but 1:1) representation of the internal Snap code.
Oh really? What is the 1:1 representation of a diff on XML in the visual code?
Representation in a programming language is a huge feature of the language, and it's particularly ridiculous to claim that it isn't for a language whose key feature is having a visual representation rather than a textual representation. An alternative representation of a programming language is a completely different programming language.
> There's no absolutely reason why the Snap UI couldn't be feeding the XML to a version control system behind the scenes, and recovering previous versions from that system at will.
Yes, but that's not even the most commonly used functionality of version control. How do you propose we do visual merges? Or are you actually proposing that we write code directly in XML?
There's no absolutely reason why the Snap UI couldn't be feeding the XML to a version control system behind the scenes, and recovering previous versions from that system at will.