4 ms·
While it could be applied to coding, our focus is on bringing features that are already well known in software workflows to people outside of software engineeri
by nilsjcbsn 2y ago
While it could be applied to coding, our focus is on bringing features that are already well known in software workflows to people outside of software engineering.
Imagine: Diffs for CAD files; Diffs for music producers; Diffs for layers; Diffs for accountants
...
-> Diffs for the whole company
Now, we need a generalized SDK to make it easy to build apps with built-in change control.
- Terretta 2y agoRight. A lot of tools, even security or access controls, seem to have no conception that git is a thing. Somewhere they all have config. This could help. Effectively, all the things that have a stateful representation that there's a reason to know versions/changes, but aren't typically thought of as "source code" (e.g., Markdown is DSL source code, but almost nobody thinks of it like that). And yes, for our own in-house tools or CRUD dashboards or full apps, we want that SDK! Even though we know git.
- nilsjcbsn 2y agoRight! The interesting part begins when you start looking at data that isn't source code. We'll achieve semantic understanding of various file formats through plugins. If you're really curious, you can follow #lix-progress on Discord -> https://discord.com/invite/gdMPPWy57R https://discord.com/invite/gdMPPWy57R