| if you already know git (or github), it'll work for books. but i doubt it's the best change-tracking system for them. too much irrelevant crap, and it doesn't cut to the heart
of those things that actually need to be done for a book. plus, most writers will never slog through learning github. to make a system that is writer-friendly _and_ does what
a book-writing change-tracking system ideally _should_ do,
you'd have to hack github so much that -- in the end --
it would have been order-of-magnitude simpler (and better)
to program a purpose-built system instead, from scratch. and yes, i told loren this from day one. he didn't believe me then. but if you ask him now, i'll bet he won't be quite so sure. and by the time he's done, i have no doubt he will agree. yes, writers need a version-control system. but no, it is most definitely _not_ github. -bowerbird |
On the other hand when using something ready like git allowed him to launch quicker. If he gets traction he can always write a new system later, if not then he has saved up on a lot of time.