3 ms·

Besides its use for the work flow for a single person developing an app I fail to see the case for this system.

• vtemian 12y ago
  It is intended for non-developers so that they can integrate their workflow with developers working on the same content. It can be used by multiple persons of course but it's not generally targeted for people developing apps or for replacing git.
  • listic 12y ago
    Same content (set of files) but different files? Here's the use case I have in mind: let's say I'm a programmer extending a game [1] built on Undum [2] engine, together with a writer who is writing a story at the same time [3] [1] The Play, A dress rehearsal gone horribly wrong, by Deirdra Kiai. http://squinky.me/theplay/ http://squinky.me/theplay/ [2] http://undum.com/ http://undum.com/ [3] Story file: view-source:http://squinky.me/theplay/theplay.js http://squinky.me/theplay/theplay.js
    • vtemian 12y ago
      If you work on the same file the content will get versioned like it would when you use command line git. Also you will get some sort of accountability for changes.
      • listic 12y ago
        And the intent is that developers can access the same data via git. Right?
        • vtemian 12y ago
          Yep.