News for hackers. Stuff that matters.
Re:Lessons learned from creating a rich-text editor with rea... by contingencies on Sunday December 13, 2020 @08:31PM (#25412436)
I guess you can have a distributed locking mechanism, either scope or line-driven.

Another option would be when there is a conflict you have a fork, and then re-merge at a later point (eg. when scope-specific changes are complete or scope is left or syntax is re-evaluated as valid), more similar to git style workflow. Which begs the question, why not just use an established RCS/VCS like git and build the interface in front of it, utilizing its built-in diff? However, this workflow probably detracts greatly from the real time intent...

Re:Lessons learned from creating a rich-text editor with rea... by SahAssar on Monday December 14, 2020 @04:27PM (#25423571)
> I guess you can have a distributed locking mechanism, either scope or line-driven

In real time? How would that solve the problems outlined in the article?

> However, this workflow probably detracts greatly from the real time intent

Seems like you understand the problem.

Re:Lessons learned from creating a rich-text editor with rea... by monroewalker on Tuesday December 15, 2020 @11:42AM (#25431927)