In this case, we're discussing a case where mark-and-sweep is used to collect cyclic references, and it's implied that there are no generations. (Because otherwise, purely relying on reference counting means that cyclic references end up leaking unless things like weak references are used.)
IE, the critical difference is that reference counting frees memory immediately; albeit at a higher CPU cost and needing to still perform a mark-and-sweep to clear out cyclic references.
It looks like each of its two reactors are a good bit more powerful than what is in an Ohio Class Submarine, but far less than what's in a Gerald R Ford class Aircraft carrier. For whatever thats worth
Kinda interesting to ask what would have gone different if the infrastructure was in place to make electric cars 'good enough' as far as charging infrastructure.
As I understand it, the core problem back then was the batteries would mass half the car and lose a third of their maximum capacity in just 500 charging cycles.
Back when cars were new, there was no infrastructure for petrol either, that was something you got in tiny quantities from a pharmacy. (The diesel engine can run on vegetable oil, but I don't think Mr Rudolf Diesel himself ever did that?)
Infrastructure requires demand, and energy density and convenience of a contemporary battery versus gas engine means that no one was going to demand batteries when ICE was an option. We only figured the downside much later.
And typically just fast RAM everywhere instead of caches, so you don't have cache misses. (The flip side is that you typically have very _little_ RAM.)
Some older ones, yeah (TeraScale comes to mind) but modern ones are more like RISC with whopping levels of SIMD. It turns out that VLIW was hard for them too.
You can you just have to ask. And that's not an oracle thing. All the commercial databases have that rule. It's too easy to make misleading benchmarks for such complicated products so that's why they do it.
NATS has a bit more in terms of durability guarantees so I have found that it hits more use cases. I'm trying to strike a bit of a balance between "use the exact right tool for the job, even if that means you have 25 different services" and "just use Postgres". I do think Postgres/Redis/ClickHouse is probably fine as well but durable streaming would be hard to give up.
