this post was submitted on 14 Feb 2026
366 points (98.2% liked)
Programmer Humor
29749 readers
319 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Based on what? It’s top notch for immutability, zero trust, proof of existence, accountability, transparency, uptime, decentralization, network resilience…
What about throughput, latency, schema modeling, query load balancing/routing, confidentiality, regulatory compliance, operational tooling? How easily can I write a CRUD or line of business service using it?
Confidentiality, regulatory compliance, schema modeling (IDLs?), query load balancing (rpc infra) and operational tooling pretty good in my world now (Solana). Throughout and latency decent now (400ms conf, couple second finality, 4k tps) but obviously the type of system that needs a trustless immutable database has tradeoffs.
How easily can you write a crud system? No clue that’s on you. A line of business service? Why the hell would that need a trustless immutable ledger. You’re barking up the wrong tree. Low level financial systems are pretty much the only thing that benefits. Small niche for proof of existence perhaps. And maybe other immutable use case things.