11–20 of 32 posts
> The standard solution to any hard problem [which is] is to find someone who solved it already and steal their answer. Reminds me a little of the Feynman algorithm. 1) Write your question into google. 2) Open the first three results. 3) Copy what you find. Does it already have a name?
1. Write down the problem.
2. Think real hard.
3. Write down the solution.
Remove that ability by constantly recording changes, and you can no longer control your code: no code review, no feature merging. Everything just becomes a giant mess. A mess that's auditable, but a mess nontheless
The whole thing is supposed to "just work" and, at version 0.8, it pretty much does, stably. But we still have a lot to do.
The reason we chose this is because it supports everything from updating your status / location / whatever to chatrooms and collaborative documents. A chess game is just a stream of type "Chess/game" which supports messages like "Chess/move" and "Chess/resign".
All the developer has to do is implement their stream type, or "tools" (components) to interact with the stream or "preview" it in listings. We provide typical tools such as "Streams/related" which automatically handles showing streams related to some given stream, and can update in realtime, allow creation of more streams, etc. The developer would jst handle incoming messages and process their effects. Also sometimes a stream might Refresh because the user, say, came back to a mobile app after it was suspended in the background. In this case the stream player or preview gets the latest state instead of "replaying" what would potentially be 100s of messages. And the whole page doesnt need to be reloaded. It all works already.
Now we are working on Offline streams. For example, a stream that has been created offline isn't shared with anyone so no one else can write to it. This means we ca handle all the persistence on the client and sync it later, when the client connects.
We do not attempt to solve issues via "heuristic" diff based sync algorithms. Instead, the source of truth is the Publishing User's server and it is also the source of chronological order of the messages. The developer never has to worry about messages arriving out of order, or something else, just use the JS API. In addition, we handle the CAP theorem by requiring consistency only per stream. If one message contains (hashed) info from another message on some other strean, we know it was posted later (like bitcoin).
In the end we plan to make this platform completely distributed and power social layer for the web like wordpress powers blogs.
So that's how wedo it!
Collaborative live programming is a pretty bad idea in the first place. There is one thing that's very important that you're missing in your analysis of "the past". All DVCS system allow the programmer to group a set of changes by commits, which constitute a consistent block of changes. Remove that ability by constantly recording changes, and you can no longer control your code: no code review, no feature merging. Ev…
Right now I am lost with git and mercurial, Gist has better visual diffing than standard repos, yet standard repos have better granular linking.
Gitchain/Mercurialchain would help the world if there was a log-long-term where every bit was actually accountable, versus our current war text processing by taking logological leads from heads without tails — depth psychology and science at logy cannot scale without being able to read granulate better.
Without finite and granular social logging currency, breakthrough commits recreate old patterns of hidden language between growths.
Without finite and granular social logging currency, breakthrough commits recreate old (forma trauma terma) patterns of hidden (problem solving without showing work hurts?) language between growths.
Collaborative live programming is a pretty bad idea in the first place. There is one thing that's very important that you're missing in your analysis of "the past". All DVCS system allow the programmer to group a set of changes by commits, which constitute a consistent block of changes. Remove that ability by constantly recording changes, and you can no longer control your code: no code review, no feature merging. Ev…
Audit trail bread crumbs are currency, for research, expression, and development at log scale. Right now I am lost with git and mercurial, Gist has better visual diffing than standard repos, yet standard repos have better granular linking. Gitchain/Mercurialchain would help the world if there was a log-long-term where every bit was actually accountable, versus our current war text processing by taking logological lea…
Earlier quoted context omitted.
Audit trail bread crumbs are currency, for research, expression, and development at log scale. Right now I am lost with git and mercurial, Gist has better visual diffing than standard repos, yet standard repos have better granular linking. Gitchain/Mercurialchain would help the world if there was a log-long-term where every bit was actually accountable, versus our current war text processing by taking logological lea…
Man, that looks an awful lot like the kind of things a bot might say.
If/when legal codes and power codes are apaths and robo swears, it might reflect realities of serialities?
If/when legal codes and power codes are apath-grammar-determination by robo swears syntaxic sugar wars, it might reflect a realities of serialities?
> The standard solution to any hard problem [which is] is to find someone who solved it already and steal their answer. Reminds me a little of the Feynman algorithm. 1) Write your question into google. 2) Open the first three results. 3) Copy what you find. Does it already have a name?
Am I confused, or is this the opposite of the Feynman algorithm? Using your variant of the Feynman algorithm, I found [1] : 1. Write down the problem. 2. Think real hard. 3. Write down the solution. [1] http://c2.com/cgi/wiki?FeynmanAlgorithm
Earlier quoted context omitted.
Audit trail bread crumbs are currency, for research, expression, and development at log scale. Right now I am lost with git and mercurial, Gist has better visual diffing than standard repos, yet standard repos have better granular linking. Gitchain/Mercurialchain would help the world if there was a log-long-term where every bit was actually accountable, versus our current war text processing by taking logological lea…
Man, that looks an awful lot like the kind of things a bot might say.