5 ms·
Version control needs to be visual and pervasive. It also needs to deal with whatever files you want to dump into it. Dropbox (as you guys mention) as well as
by ThinkBeat 3y ago
Version control needs to be visual and pervasive.
It also needs to deal with whatever files you want to dump into it.
Dropbox (as you guys mention) as well as Google Drive and OneDrive and I am certain a lot of others have already implemented.
All files are versioned and for the most part you dont have to do anything.
All of this is clear with it comes to Git, with the 100+ different programs
trying to give people a visual experience, over cryptic and inconsistent
command line interface.
I am working on a simple proof of concept on a new way to visualize changes in code. Still early. It is far from trivial, but I think it is needed.
There is a good chance I will fail of course. But if enough people think about
it someone will figure out a better way than what we have now.
Well some of the work has already been done, for a long time in more integrated
IDEs where the environment is much more interactive and interlaced.
- jsunderland323 3y agoI'd be happy to hear about your project and share my learnings if you want to schedule a time to talk. I've put a tiny bit of thought into this problem and would love to pass on what I've learned. The way I originally conceptualized floro was a way to version anything without requiring plain-text (ie. higher order versioning). I've strayed quite a bit from that belief and I think there's a lot of complex trade-offs involved in version control and what makes sense for specific use-cases. Floro would be trash for game development but that is an industry that sorely faces tough versioning problems involving graphical data. Please feel free to reach out to me if you do want to chat. The discord for floro is listed on the website but you can also just check my HN bio for my email.
- hdarshane 3y agoCheck out some of the work at https://www.inkandswitch.com/patchwork/notebook/ https://www.inkandswitch.com/patchwork/notebook/
- jsunderland323 3y agoI love ink & switch! I think Martin, Geoffrey, and the whole team are crazy smart. There's a whole bunch of approaches to universal versioning and I think floro is one of a few upcoming techniques in the ether. From my limited understanding of their approach, it looks like they're going to be really focused on things like rich text diffing, which is not something I think floro is particularly well suited for. I think floro is really great for things that end up getting consumed as code rather than something like note-taking. e.g. static assets & i18n. It's really exciting to see this space actually beginning to blossom though!