"Hello main office, I have seen a rumor on Instagram that a bridge has collapsed. Should I stop all traffic through this region due to this shitpost?"
"Hi please don't - we've had three different trains go through there already. There is no loss of signaling in the area, electrical and infrastructural connections are responding appropriately. We will be sure to contact other drivers and let them know about this"
Beyond the fast entry (no parentheses), I like RPN because I find it a more intuitive way of working with numbers.
I do not need to think about my operation before I start inputting numbers. I can type in the numbers I'll need, and while seeing them I run operations on them.
There's nothing specific to read about it, just plenty of anecdotal evidence. People use connection pools because connecting to _remote_ databases is slow. SQLite _is not remote_. It's _in-process_ and _fast_. Any connection-pool _adds_ to the amount of work needed to get an SQLite instance going.
It's _conceivable_ that pooling _might_ speed it up _just a tad_ for databases with _very large schemas_ because parsing the schema (which is not done at open-time, but when the schema is first needed) can be "slow" (maybe even several whole milliseconds!).
I stopped using Nextcloud when the iOS app lost data.
For some reason the app disconnected from my account in the background from time to time (annoying but didn't think it was critical). Once I pasted data on Nextcloud through the Files app integration, it didn't sync because it was disconnected and didn't say anything, and it lost the data.
I never had data outright vanish, but similar to the comment you replied to, it was just unreliable. I found Syncthing much more useful over the long haul. The last 3 times I've had to do anything with it were simply to manage having new machines replace old ones.
Syncthing sadly doesn't let you not download some folders or files, but I just moved those to other storage. It beats the Nextcloud headache.
Oh no worries, yeah that works like gitignore, I’m talking more like how Nextcloud and Dropbox let you like, have a list of folders and checkboxes where you can be like “this machine doesn’t need my family photo collection synced to it” kinda thing. Which to my knowledge syncthing doesn’t have.
“This machine doesn’t need my family photo collection synced to it” is .stignore. It’s a bit confusing because .stignore is more like .git/info/excludes than .gitignore in that it’s not synced between machines[1]. (If you wanted a synced ignores file then you need to #include that file from each machine’s .stignore manually.) And what’s ignored on one machine doesn’t then need to be ignored on the others, which will still sync it between themselves in that case. So no pretty checkboxes, but echo /Photos >>.stignore on the machine in question and you should be good (including to delete the Photos subdirectory on that machine).
I use Arc which I've recommended on HN a few times. https://news.ycombinator.com/item?id=38662095 As a power user I find that it could be buggy but the developer behind it responds quickly on the forum. The developer also made another app with fewer features but FOSS: https://github.com/sobri909/ArcMini and it's been on my TODO list to use that as the basis to create my own location tracking app (I have some UI ideas for such an app in my mind).
The battery life impact is quite large. The iOS battery tool reports on the order of 5% to 10% but I think subjectively it feels much more than that. Getting GPS signals itself is IMO a bigger power draw than the app writing some time series data into a SQLite database (it defers expensive processing until the app enters the foreground).
