31–40 of 118 posts
How big do you think the intersection is of people who can use git and people who want to use Microsoft Word?
As enterprises seem to take up using git, this is probably a ton better than storing Word docs in git, I think. So not so few people :-)
I like the idea, let's see how it plays out.
Took me a while of reading here to realise, there's no git here. This is a seperate thing that cannot be integrated with your existing stuff, if you're already using Git. I'd like to have the option of Word documents in Git but I don't want a whole other system just for the special snowflake that is Word as I'm already using Git for managing LaTeX documents and doing that entirely on my own infra.
If you do use it, feedback is always appreciated (I'm one of the Overleaf founders), thanks.
Earlier quoted context omitted.
Word is tons more powerful than Google Docs, has add-ins, way more formatting and styling. In my mind, Google Doc is not a direct competitor to Word when it comes to professional editing and writing.
Ideally, styling should have nothing to do with editing or writing. You're talking about print (or PDF/static image) publishing, I guess?
Other folks have provided a bunch of commentary on the validity of your idea, so I won't address that.
BUT: if this is a good idea, your pricing is far too low for a niche product like this. $10 (or 10 quid) is too low a monthly fee for pretty much any product marketed as a business product. 10 per seat per month is probably also too low, but would be a better starting point.
Likely objection: "But Spotify is only $10/mo!!!" Spotify has the much larger addressable market of people with hearing and an Internet connection. Even Dropbox has a higher price point for business users, and it also has a far larger addressable market.
If you're building something that's useful for people, charge more.
Good luck!
If you save your LibreOffice documents in flat XML format, (e.g. fods, fodt instead of ods, odt), placing them under version control becomes slightly less annoying — the diffs become at least _potentially_ human readable.
See also:
http://blog.riemann.cc/2013/04/23/versioning-of-openoffice-l...
https://listarchives.libreoffice.org/global/users/msg48067.h...
I tried doing something like this a couple of years ago by embedding an actual git repository inside a docx or ODF file. Unfortunately, most popular word processing suites back then trashed the git directory instead of leaving it alone (as they should, according to the standards)
Most law firms (and I would guess all major ones) will not allow uploading of client documents or work-product to any cloud provider, let alone an unproven start up. This risk is frankly way too high.
The only way I see this happening in the legal context is if it can be run from the firm's servers with all data hosted locally.
So Google Docs? It seems close enough. What's the main advantage over Google Docs?
The addition of tags/versions is something that I would kill for in Google Docs. It would make life so much easier in my current role if we had the ability to tag a version so that you can easily see a diff between that specific, tagged version and the current version (rather than just seeing diffs over time as it is currently implemented).