Patch-based stuff is simply based on obsolete 30 yrs old assumptions. Why should you need a combinatorial algorithm to detect changes if you can track every user's action? etc etc
"According to an insider [10], in 6 months since the projects’s launch the possibility of working with partial histories is not implemented yet; pages are bootstrapped with their complete histories."
What I will concede is that their OT implementation is probably not perfect yet. If you read the comments on some transformation functions on their Java code, they shown concern and do extra logging in hopes to track unexpected issues they haven't solved yet.
Some unexpected issues are not solved for past 20 years.
I do not attack annotations or XML per se. The general approach "neither thing is precisely OK, so let's use both" seems questionable to me.
I believe, XML is complex enough, so why do we need XXML?
Finally, by using annotations they recognize that XML nesting is a pain in the ass, but they did not solve the problem, just sort of relieved it.
Actually, I doubt a lot, whether XML is actually carrying some useful load in the Wave. But the last one is just a feeling.
OT is a dead end. The problems they struggle with could be trivially bruteforced by employing unique symbol identifiers. http://bouillon.math.usu.ru/articles/ctre.pdf