5 ms·
The "problem" with these systems is sharing changes - if I change the system you share with me for myself, it's really hard for someone to use those changes alo
by vertex-four 6y ago
The "problem" with these systems is sharing changes - if I change the system you share with me for myself, it's really hard for someone to use those changes along with other changes. Integrating changes together involves handling merge conflicts in code we don't necessarily understand.
I think separating the data the system operates on from a series of smaller systems is the key here.
- chr15m 6y agoYes, that is a problem. It is one which is solved by git and other version control software. If you are building something with an online editor like Slingcode and you get to the point where change management becomes an issue then it is probably time to switch to a more comprehensive development environment.
- sitkack 6y agoExcellent work! I am happy for you, this is really cool. Take a look at posts, blogs and videos by Joe Armstrong, one of the inventors of Erlang. Some things that stand out are "immutable code" and globally accessible code. The other one is the research around CRDTs. https://dl.acm.org/action/doSearch?AllField=crdt https://dl.acm.org/action/doSearch?AllField=crdt