samuelstros
Joined 4 years ago
Karma
578
Submissions
175
Member since
Dec 3
founder of opral.com
View on Hacker NewsRecent submissions
Comment · 10 days ago
because Rust will be faster and can compile to WASM which the TS ecosystem needs
Comment · 11 days ago
At this point, why invest further in TSGO?
No matter how many optimizations can be ported from tsrs to ts-go, Rust will be more efficient and enable the WASM use case.
The premise of porting the compiler from TS to GO was ease of migration due to Go's garbage collector. That doesn't hold anymore? AI doesn't care how hard or easy a migration is if a test suite exists.
Comment · 1 month ago
yes. unfortunate. we choose the name before they launched. by the time they launched, lix (vcs) was already used in prod
Comment · 7 months ago
track the source of the asset and it works. take ui design. dont track the svg. track the design file itself
Comment · 7 months 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.
Comment · 7 months 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 entities instead of the binary blob. You can apply the same logic to files used in game development.
The hard part is making this fast enough. But I am working on this with lix [0].
Comment · 8 months 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 -> parse -> diff is too slow.
The parse and diff step need to get out of the hot path. That semi defeats the idea of a VCS that stores ASTs though.
Comment · 8 months ago
Yep “stripe couldnt build it because they rely on http ingestion”. Lol.
Comment · 8 months 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?