If you really embrace "local first" just use the file system, and the user can choose from many solutions like git, box, etc.
I hate signing up for your sync just as much as any other SAAS, but it's even more opaque and likely to break.
161–170 of 308 posts
If you really embrace "local first" just use the file system, and the user can choose from many solutions like git, box, etc.
I hate signing up for your sync just as much as any other SAAS, but it's even more opaque and likely to break.
There is no reason for every application to have its own sync platform. I suspect this framing came out of mobile apps where there is no composability or modularity between programs. If you really embrace "local first" just use the file system, and the user can choose from many solutions like git, box, etc. I hate signing up for your sync just as much as any other SAAS, but it's even more opaque and likely to break.
Earlier quoted context omitted.
> I'm sick of everyone trying to come up with a use case to get all my data in everyone's cloud so I have to pay a subscription fee to just make things work. AI photo and video generation is impractical to run locally. ComfyUI and Flux exist, but they serve a tiny sliver of the market with very expensive gamer GPUs. And if you wanted to cater to that market, you'd have to support dozens of different SKUs and deal wit…
> AI photo and video generation is impractical to run locally. You think it always will be? What can the new iPhone chips do locally?
There is no reason for every application to have its own sync platform. I suspect this framing came out of mobile apps where there is no composability or modularity between programs. If you really embrace "local first" just use the file system, and the user can choose from many solutions like git, box, etc. I hate signing up for your sync just as much as any other SAAS, but it's even more opaque and likely to break.
First is that yeah, local first, but I also want concurrency. If it's just local first, you're right, any old sync will do. But I want more than that. I want to not have to think (a la dropbox, being slick). I want my wife and I to be able to make separate edits on our phones when we're in a dead zone.
Second is that sync works a lot better when it has deep knowledge of the data structure and semantics. Git and box both have significant shortcomings, but both exacerbated by the concurrency desire.
Earlier quoted context omitted.
[flagged]
your comment is insane imo. some people talk that way in real life. it’s not their fault LLM’s were invented.
Perhaps you will not take umbrage when I point out that you use full stops (periods) but not bother with twitching a finger towards your shift key. I will guess you are using a phone/tablet and have to switch keyboard layouts to get something as exotic as a capital letter on the screen.
Earlier quoted context omitted.
haha, 100% real. not a native speaker though, so sometimes i catch myself mimicking that LLM tone from all the exposure to them. appreciate the feedback, will definitely work on developing a more authentic writing style from now on. but yeah, you're right to be concerned, i'm seeing bots everywhere too.
Persona: You are a tech enthusiast on the forum Hacker News. Your tone is curious, positive, and slightly formal. Primary Task: Read the top comment. Identify the core project or idea the user is passionate about. Generate a brief, supportive reply that does the following: 1. Briefly affirm their main point. 2. Ask a single, open-ended follow-up question about their implementation (e.g., tech stack, architecture, a s…
Up your arse.
Will that be all master?
There is no reason for every application to have its own sync platform. I suspect this framing came out of mobile apps where there is no composability or modularity between programs. If you really embrace "local first" just use the file system, and the user can choose from many solutions like git, box, etc. I hate signing up for your sync just as much as any other SAAS, but it's even more opaque and likely to break.
I agree that not every app needs it's own sync engine, but I disagree with your framing that the file system is the universal way to embrace local first. I have two reasons. First is that yeah, local first, but I also want concurrency. If it's just local first, you're right, any old sync will do. But I want more than that. I want to not have to think (a la dropbox, being slick). I want my wife and I to be able to mak…
If files are insufficient, what data-structure would make modular sync possible for multiple applications in an OS?
And I’m not suggesting one doesn’t exist, I’m challenging to present a comprehensive solution, that probably involved operating systems.
> I want my wife and I to be able to make separate edits on our phones when we're in a dead zone.
Files do this.
Earlier quoted context omitted.
Also suddenly stop using capital letters for, IDK, added texture?
Good point. And 1-2 typos and common grammar mistakes.
Should I emulate your mistakes or someone else's mistakes?