Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
samuelstros
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
31.
▲
by
samuelstros
9mo ago
Git only works for text files. Everything else is a binary blob which, among other things, leads to merge conflicts, storage explosion, and slow git operations
32.
▲
by
samuelstros
10mo ago
> RFC Hub has so much functionality that it's difficult to explain it all on the homepage That's what I meant with overwhelming / too niche. It seems like you intend to productize the RFC process e2e. But most "time c
33.
▲
by
samuelstros
10mo ago
Initial reaction: Looks too complicated & too niche of a problem to appeal to a sustainably large user group. GDocs might be annoying to track who read the RFC etc. etc. but everyone is familiar with it. I write RFCs, I share RFCs and y
34.
▲
by
samuelstros
1y ago
I recommend adding an installable executable. It seems like you are expecting people to clone your repo and then run it locally? Take a look at Monitor Control how they structured their GitHub Readme and release page to download a dmg http
35.
▲
by
samuelstros
1y ago
does a framework like vercel's ai sdk help, or is handling the loop + tool calling so straightforward that a framework is overcomplicating things? for context, i want to build a claude code like agent in a WYSIWYG markdown app. that&#x
36.
▲
What makes Claude Code so damn good
(minusx.ai)
469 points
by
samuelstros
1y ago
|
304 comments
37.
▲
by
samuelstros
1y ago
can you elaborate on what versioning issues you are facing?
38.
▲
by
samuelstros
1y ago
100% agree with the sentimment. markdown is hell as a format for editors :D the effort it takes to serialize and parse markdown into an AST that rich text editor frameworks reliably operate on takes months. been there, done that. the majo
39.
▲
by
samuelstros
2y ago
> The only reason people build “apps” in the browser to begin with is because it simplifies the development for the engineering team. Easier to ship, easier to update, write once, etc. Sometimes the user benefits, but rarely. Interesting
40.
▲
by
samuelstros
2y ago
What makes you think the browser as OS is silly?
41.
▲
by
samuelstros
2y ago
nice, "run JS without (browser) runtime" is coming. perforr, jaws, or another project will eventually succeed.
42.
▲
by
samuelstros
2y ago
Why did you pivot away from localization? See their old launch https://news.ycombinator.com/item?id=31166924
43.
▲
by
samuelstros
2y ago
That's a good tip. I was wondering how SQLite avoids page fragmentation. The answer is "it depends," but VACUUM is to the rescue. What are your reasons for advocating for SQLite as a filesystem abstraction?
44.
▲
by
samuelstros
2y ago
Today i learned that HN has a nesting limit. @surrealize i fixed the username https://github.com/opral/monorepo/commit/7dc1f3c806bd89c6d68...
45.
▲
by
samuelstros
2y ago
Yes. The runtime was not affected. Hence, the ts-expect-error. Still nice to have the ts-expect-error fixed :)
46.
▲
by
samuelstros
2y ago
You are now forever in our git history https://github.com/opral/monorepo/commit/58734e11e51d8e20092 .... the ts-expect-error was indeed fixed by your suggestion
47.
▲
by
samuelstros
2y ago
Yes. We looked at all version control systems (fossil, pijul, jj, git, darc, sapling). None provide what we need: - target the browser - supports any file format, not just text files - understands changes, not just versioning of files - sui
48.
▲
by
samuelstros
2y ago
the types kysely implemented are crazy. even custom where clause like this one [0] are typesafe :O [0] https://github.com/opral/monorepo/blob/99356e577f558f4442a95...
49.
▲
by
samuelstros
2y ago
We also came around to dumping files into SQLite instead of dealing with the filesystem (and git) for the lix change control system. This article touches on problems we encountered: https://opral.substack.com/i/15005423
50.
▲
by
samuelstros
2y ago
I wish we could talk about your use case later at Local Thirst. But ... I lost my passport and won't be able to make it. Another time!
51.
▲
by
samuelstros
2y ago
Yeah bummer that Safari and Firefox are blocking any origin file access for security reasons. > when the company owning the DNS records for that origin goes out of business. Likely not a problem. Local data in OPFS is synced with a remot
52.
▲
by
samuelstros
2y ago
OPFS works in Safari, see this demo app https://csv-n2qj.onrender.com/ . What doesn't work in Safari and Firefox is (non sandboxed) access to the files of a user. OPFS is sandboxed.
53.
▲
by
samuelstros
2y ago
Webapps will work locally soon. Say hello to OPFS https://web.dev/articles/origin-private-file-system . Works surprisingly good, see this demo app https://fink2.onrender.com/
54.
▲
by
samuelstros
2y ago
Using lix change control to plot changes over time is a neat idea!
55.
▲
by
samuelstros
2y ago
Hm. Not convincing. Disclaimer: I am the founder of Opral ( https://inlang.com/ && https://lix.opral.com/ ) The idea of parsing source code to auto inject translations, especially while leveraging mac
56.
▲
by
samuelstros
2y ago
While building lix change control I figured out that collaboration was/is the driver behind local to cloud. A secondary reason is compute. If a system exists that enables (distributed) collaboration on files, the appeal of cloud-based
57.
▲
by
samuelstros
2y ago
Agree. What’s your reasoning?
58.
▲
by
samuelstros
2y ago
interesting. that was not the case in 2019 when i did a bit of data science.
59.
▲
by
samuelstros
2y ago
are you running into issues while building on top of git & github? i assume that you need to teach data science people git/github
60.
▲
by
samuelstros
2y ago
i assume that editing csv's is coming later? i can upload a csv but not edit it
More ›