At some point you start wondering if there's any tool with conditionals and some form of persistent state that ISN'T Turing complete. The bar seems way lower than most people assume. Reminds me of the mov-is-Turing-complete result from a few years back.

Scammers will use stolen identities or shell companies. They already do this on the Play Store itself. The $25 fee and passport upload haven't prevented the flood of scam apps there.

Meanwhile F-Droid's model (build from source, scan for trackers/malware) actually provides stronger guarantees about what the app does. No identity check needed because the code speaks for itself.

The permission-based approach someone mentioned above makes way more sense. If your app wants to read SMS or intercept notifications, sure, require extra scrutiny. But a simple calculator app or a notes tool? That's just adding friction for no security benefit.

More broadly: faster boot times (sub-second POST is common), no vendor bloat or hidden phone-home behavior in the firmware, and you can actually audit what runs before your OS loads. That last one matters more than people think. Your BIOS has full access to everything on the machine before any OS-level security even starts.

Now I pick one tool, learn it properly, and ignore everything else until my current setup actually fails me. Most "AI news" is just leaderboard shuffling that doesn't change how I work day to day.

The real overload isn't the technology. It's the marketing cycle around it. Every week someone announces the new best model, and if you're on Twitter it feels like you're falling behind by not switching. You're not.

Practical filter: if a new release doesn't solve a problem I currently have, I skip it entirely.

Tailscale and similar overlay networks have made the "accessible from anywhere" part way easier than it used to be. The missing piece is still discovery. RSS was the closest we got to decentralized discovery, and we collectively let it rot. Maybe it's time to bring it back properly.

Curious about latency overhead for the common case. On a direct-to-shard read where no rewriting happens, what's the added latency from going through PgDog vs connecting to Postgres directly? Sub-millisecond?

The real cost was never the code itself. It was the decision-making around what to build. That hasn't gotten cheaper at all.

Comments URL: https://news.ycombinator.com/item?id=47124599

Points: 1

# Comments: 2

The real story here isn't Hetzner being greedy. It's that AI companies are vacuuming up every DRAM chip on the planet and the rest of us get to pay the tax. I priced out a RAM upgrade for my home server last week. Same kit I bought 8 months ago for 90 EUR is now 400+. That's not normal market dynamics.

What worries me more is the second-order effects. Startups that would normally spin up cheap VPS instances to prototype and iterate now face meaningfully higher costs at the exact stage where every euro matters. The "just deploy it" culture that made European indie dev scene so productive was built on sub-10 EUR/month boxes. Those days might be over for a while.