Cool idea - seems like a pain supporting docx and other MS formats that are locked down. PDF, adobe files, mp3, etc. Like agony close to impossible levels of pain. You're showing off doing a CSV which at that point me and my team could just use google sheets or use git + csv file and reopen after commits. BASICALLY I see the idea and wish it exists but this seems basically impossible to widely support and unless this is also supporting all my files or more functional then using google sheets idk why anyone would use it.
great feedback. we already got a sqlite/binary format working in lix. gonna follow up with additional file formats like docx, pdf, mp3, later. docx & co are open formats. certainly doable but the spec is 500 pages long. what file format would give you confidence that lix is generalizable that is not a 500 page spec?
@@samuelstroschein I guess what I'm highlighting is that teams that there's two components to this: Live editing + diffing Without looking fully into your implementation I would say this should fully do everything git does or extend on it. Like uh ideally what you showed off would be if the format is fully supported, if not then you could just do a jank workflow like you can with multiple people using git to edit a csv right now?
Cool idea - seems like a pain supporting docx and other MS formats that are locked down. PDF, adobe files, mp3, etc.
Like agony close to impossible levels of pain. You're showing off doing a CSV which at that point me and my team could just use google sheets or use git + csv file and reopen after commits.
BASICALLY I see the idea and wish it exists but this seems basically impossible to widely support and unless this is also supporting all my files or more functional then using google sheets idk why anyone would use it.
great feedback. we already got a sqlite/binary format working in lix. gonna follow up with additional file formats like docx, pdf, mp3, later. docx & co are open formats. certainly doable but the spec is 500 pages long.
what file format would give you confidence that lix is generalizable that is not a 500 page spec?
@@samuelstroschein I guess what I'm highlighting is that teams that there's two components to this:
Live editing + diffing
Without looking fully into your implementation I would say this should fully do everything git does or extend on it.
Like uh ideally what you showed off would be if the format is fully supported, if not then you could just do a jank workflow like you can with multiple people using git to edit a csv right now?