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.
Based on what? It’s top notch for immutability, zero trust, proof of existence, accountability, transparency, uptime, decentralization, network resilience…
Yeah all I have is a useless summarize button that I just don’t click. If I needed it I would, seems useful. But I don’t really need it for anything. I like to read.
Not necessarily. If this period, more hybrids were sold instead of gas cars over the prior period, it would result in this threshold also being crossed. In addition, less cars over all could be sold.
To objectively know that more elec were sold you’d have to have the prior month.
I was doing enterprise stuff. Was a weird time dodging bullshit like j2ee “javabeans” stuff but picking out the signal from the noise.
Mostly did websphere hosted jsp stuff. Moved to that from… check it… J++. It was right in the midst of the MS v Sun lawsuit craziness.
Only did 2 years before a huge MS .NET enterprise pivot back to the dark side where I stayed for 20 years before jumping to embedded and rust blockchain stuff.
This is correct. And it’s always possible to bypass and do things illegal. Just like pirating.