samuelstros

7 ms·

1.
by samuelstros 7d ago
yes. unfortunate. we choose the name before they launched. by the time they launched, lix (vcs) was already used in prod
2.
Lix – Embeddable version control/repository system(lix.dev)
2 points by samuelstros 7d ago|2 comments
3.
Show HN: Flashtype – Markdown editor for Claude and Codex with in-line diffs(flashtype.com)
5 points by samuelstros 3mo ago|0 comments
4.
Lix v0.6 – Embeddable version control system for AI agents(twitter.com)
2 points by samuelstros 4mo ago|0 comments
5.
AgentCRM – Headless CRM for Claude Code(github.com)
17 points by samuelstros 4mo ago|0 comments
6.
From CVS to Git, thirty years of source control, lived from inside(evilgeniuslabs.ca)
4 points by samuelstros 5mo ago|0 comments
7.
by samuelstros 6mo ago
track the source of the asset and it works. take ui design. dont track the svg. track the design file itself
8.
by samuelstros 6mo ago
Simple left or right merge. One overwrites the other one. The appeal or structured file formats like .docx, .json, etc. Images are unstructured and simple "do you want to keep the left or right image" is good enough.
9.
by samuelstros 6mo ago
Improving on "git not handling non-text files" is a semantic understanding aka parse step in between the file write. Take a docx, write the file, parse it into entities e.g. paragraph, table, etc. and track changes on those entiti
10.
by samuelstros 7mo ago
How do you get blob file writes fast? I built lix [0] which stores AST’s instead of blobs. Direct AST writing works for apps that are “ast aware”. And I can confirm, it works great. But, the all software just writes bytes atm. The binary -&
11.
Building an AI agent for spreadsheets – 4 months of learnings(github.com)
1 points by samuelstros 7mo ago|0 comments
12.
by samuelstros 7mo ago
Yep “stripe couldnt build it because they rely on http ingestion”. Lol.
13.
by samuelstros 8mo ago
Oh interesting. Checks sound similar to lix validation rules [1]. We were coming from a an application perspective where blocking the users intent is a no-go. Do you have a link to a discussion where the JJ community is discussing checks? [
14.
by samuelstros 8mo ago
oh i didn't know that claude code has a desktop app already
15.
by samuelstros 8mo ago
It's basically what Emdash ( https://www.emdash.sh/ ), Conductor ( https://www.conductor.build/ ) & CO have been building but as first class product from OpenAI. Begs the question if Anthropic will fol
16.
by samuelstros 8mo ago
The SSIS use case is a good one for lix. Write an SSIS plugin (essentially just parse the XML) and lix can track the xml props in the SSIS package. Opposed to line by line stuff that git does.
17.
by samuelstros 8mo ago
> Knowing what the actual semantic deltas are in binary files (what your doc examples claimed) is hard. Hm that is what lix provides? SQL is just the interface to query the deltas. Anyhow, lesson learned. The primary use case for lix is
18.
by samuelstros 8mo ago
I think our goals indeed differ. > How often are binary files being diffed? How long does it take to materialize? How long to run a diff algorithm? If version control is embedded in an app, constantly. Imagine a cell in a spreadsheet. An
19.
by samuelstros 8mo ago
It can but the plugins are not developed for production readiness yet. I should clarify that. The way to write a plugin: Take an off the shelf parser for pdf, docx, etc. and write a lix plugin. The moment a plugin parses a binary file into
20.
by samuelstros 8mo ago
Does the following make more sense to you in respect to SQL? Lix uses SQL databases as storage and query engine. Aka you get a filesystem on top of your SQL database that is version controlled. Or, the analogy to git: Git uses the computers
21.
by samuelstros 8mo ago
Merge algebra is similar to git with a three way merge. Given that lix tracks individual changes, the three way merge is more fine grained. In case of a conflict, you can either decide to do last write wins or surface the conflict to the us
22.
by samuelstros 8mo ago
Thanks for the feedback. AI agents are the pull right now to why version control is needed outside of software engineering. The mistake in the blog post is triggering comparisons to git, which leads to “why is this better/different tha
23.
by samuelstros 8mo ago
Indeed, if lix were to target code version controlling, incompatibility with git is a “dead on arrival” situation. But, Lix use case is not version controlling code. It’s embedding version control in applications. Hence, the reason why lix
24.
by samuelstros 8mo ago
> But then the first thing it talks about is diffing files. Which honestly shouldn’t even be a feature of VCS. That’s just a separate layer. There is nuance between git line by line diffing and what lix does. For text diffing it holds tr
25.
by samuelstros 8mo ago
Learnings from the comments so far: I need to refine the positioning of lix. Lix is not a replacement for git. Nor does it target version controlling code as the primary use case. A better positioning might be "version control system a
26.
by samuelstros 8mo ago
Yes. The tracking works via plugins to keep it generic. Here is a rough illustration: File change -> Plugin (detects changes) -> Lix It works surprisingly well because most standard file formats have off the shelf parsers. Parse a fil
27.
by samuelstros 8mo ago
Hi, I'm the creator of lix. Lix doesn't target code version control. It can be used for it. But the primary use case is embedding version control in applications. Such an application can be an AI agent that modifies files which en
28.
by samuelstros 8mo ago
Correct. Lix has been developed with the embedded use-case in mind. Someone can write a CLI for it. Though, the primary use case is not code version control but embedding into applications
29.
by samuelstros 8mo ago
Depends on the diff you render and what the plugin tracks. In general, lix gives in API to track changes in any file format (via plugins). The "diff noise" thus depends on a) the plugin i.e. does it track them metadata? and b) wha
30.
by samuelstros 8mo ago
Holy moly. I just went to bed. Checking my phone for last time. Opening hackernews for "one last scroll" and see lix, my project, popping up here. Going through the questions now. So much for going to bed.

More ›