This article doesn't highlight the benefit of Fluid very much and is essentially comparing apples and oranges so I just had to post a comment to make this clear to other readers.
One cannot compare a REST API with a change event of "{ title: "hello alice!" }" to a (Fluid) change event of "Replace characters at position 6, new content: "Alice". The latter simply contains significantly more information than the former, thus making it easier to perform collaborative editing. The protocol (REST) itself is not the problem here, but rather the representation of the event. Once could just as well put the same information in a REST API and achieve the same functionality (without using Fluid).
This article doesn't highlight the benefit of Fluid very much and is essentially comparing apples and oranges so I just had to post a comment to make this clear to other readers.
One cannot compare a REST API with a change event of "{ title: "hello alice!" }" to a (Fluid) change event of "Replace characters at position 6, new content: "Alice". The latter simply contains significantly more information than the former, thus making it easier to perform collaborative editing. The protocol (REST) itself is not the problem here, but rather the representation of the event. Once could just as well put the same information in a REST API and achieve the same functionality (without using Fluid).