> we just wrote proprietary files to disk
That alone is a terrible thing. Open formats are so much more user friendly
1,562 karma · joined November 23, 2016
That alone is a terrible thing. Open formats are so much more user friendly
What's special about SQLite is that it already solves most of the things you need for data persistence without adding the same kind of overhead or trade offs as Postgres or other persistence layers, and that it saves you from solving those problems yourself in your json text files...
Like by all means don't use SQLite in every project. I have projects where I just use files on the disk too. But it's kinda inane to pretend it's some kind of burdensome tool that adds so much overhead it's not worth it.
- Lets me deploy stateless containers easily
- Let’s me leverage the NAS for local redundancy and a more centralized place to do backups
- When a project grows it’s easy to promote it to use a hosted S3
- Local S3 becomes a target for Litestream and Restic
- Developing against the local fs and then handling file storage is a huge friction, unless I’m using something like Rails that already has a good abstraction
Like `jj commit -m 'Feature A' file1 file2` then `jj commit -m 'Feature B' file3 file 4`
If you're in Love and/or control the environment you're free to bring in whatever libraries you want. Or to build your wrapper to support multiple files from the user.
Like you could suffer from a bad embedded scripting setup with any language. Granted if it was embedded Python or Javascript you would get a bit more for builtin if they embed a full implementation. But also embedding Lua with support for user supplied libraries is less effort than embedding a whole Python/JS runtime
A painter who does a bad job setting up a ladder is going to have a bad time, a lone ATC operator having a heart attack potentially puts multiple large aircraft full of people in danger...
> But people just want to compare it to building a cli tool in go or rust.
This seems like the key. HN is definitely biased towards simpler, smaller tools. (And that's not a bad thing!). The most compelling JVM stories I hear are all from much larger scale enterprise settings.
Kafka being a good example. It's very good at what it does, but painful to manage and usually not worth the pain for anyone who's not in a mega enterprise.
Because in my experience as of 2026, Java programs are consistently among the most painful or unpleasant to interact with.
You don’t suddenly owe taxes you maybe can’t afford when inheriting the family house.
You can afford those taxes when selling it for a massive profit so you should owe then. Likewise for realizing gains by taking a loan
It seems like this workflow suffers the same problem as Alexa and Amazon dash buttons: consumers don't typically want the computer to just go buy things for them with no oversight. At least I don't.
Adding a checkout step would make this more plausible to me. "Agent, go find the most efficient dishwasher under $600" where it adds its recommendation to a cart, or even "Find me the best dishwashers under $600" where it creates a catalog page with its recommendations and an easy checkout process with whatever store is actually providing.
Annoying that it happened. Annoying that Reddit mods are aggressively removing the discussion. Annoying that HN comments here are immediately jumping to Spotify hate and the sky is falling.
Imagine if we all assumed every AWS outage meant that AWS was cancelled.
---
The responses in this thread are truly disappointing. Spotify can be bad and have vibecoding issues and we can still have a rational discussion rather than just jumping on the complaint bandwagon and panicking. I guess at least eventually real comments rose to the top.
The project is ~4 years old. Screen sharing is still a work in progress. It's been a while since I tested it myself but you can still see plenty of reports of it being buggy and slow.
Basically it gives of major bike shedding impressions.
But suggesting "Why not just try remembering lol" isn't really a valid criticism of the process. What you said here is a real criticism that actually adds to the conversation.
Common internet tropes include both "look at this forgotten jar that's been in the back of my fridge since 1987" and "doesn't it suck how much food we waste in the modern world?"
Nearly every modern invention could be dismissed with this attitude. "Why do you need a typewriter? Just write on paper like the rest of the world does."
"Why do you need a notebook? Just remember everything like the rest of us do."
That's essentially exactly what they're trying to solve for although focused on the Twitter use case rather than Discord. And also one of the key advantages of ATProto over ActivityPub.
Like at least suggest old school forums, IRC, or usenet.
Does it have proper support for opening an external editor (via $EDITOR like nano, vim, etc?)? I ran into issues with that in Ink and had to switch over to Bubbletea, but I'd love to use Ruby instead of Go
Why would one pick a TinyPilot over NanoKVM or JetKVM?
With RDP/VNC what do you do if the machine fails to boot? Or RDP stops working for some reason and you can't SSH in?
Or for installing a headless OS on a new machine.
I'm sure there are more specific usecases as well but that's what I mainly use remote KVM devices for at home.
I've been exploring JJ mainly for its slightly different approach to change tracking (~every change gets tracked, at least initially, rather than just commits).
Stacked PRs also look interesting but I haven't had an occasion to try them out yet.
Before Docker you had things like Heroku and Amazon Elastic Beanstalk with a much greater degree of lock in than Docker.
ECS and its analogues on the other cloud providers have very little lock in. You should be able to deploy your container to any provider or your own VM. I don't see what Dynamo and data storage have to do with that. If we were all on EC2s with no other services you'd still have to figure out how to move your data somewhere else?
Like I truly don't understand your argument here.