2 ms·
Can I offer a suggestion - focus on non-code developer use-cases. It is still wildly difficult to integrate a VCS system into a document-based application, ye
by badjuju 3y ago
Can I offer a suggestion - focus on non-code developer use-cases. It is still wildly difficult to integrate a VCS system into a document-based application, yet this could improve many, many engineering and science applications that rely on text files (simulation configurations, pre- and post-processing setups, semi-manual entry data-backed "dashboards", etc). This is a problem that really needs solving and I don't see anything out there that makes it approachable.
Having built this myself (hacked on top of git) for an engineering analysis platform in the Energy Space, I'd say a good UI (even simpler than GitKraken) and an "just works" integration would be a massive win.
Just my 2 bits.
- BlackjackCF 3y agoI think this is a great approach. Just looking at the comments here - I'm not sure how many devs would jump for a git replacement. However, anything that solves version control for all of the non-code cases is VERY compelling.
- sasham 3y agoThanks for the feedback! We actually encountered a similar usecase. SaaS tools that need to version user-generated data and configurations. We're offering an API so this can be done easily. What you offer can also be done. I'm not sure it's a huge market though, meanwhile lots of developers that can't work with Git (e.g. games) are looking for solutions, we're seeing a real need there. But we might branch out to other things, for sure.