3 ms·
> Performance-sensitive applications are still going to go for something native. What’s up with Java in HFT stuff then? I’ve never understood this: from what I
by the_only_law 4y ago
> Performance-sensitive applications are still going to go for something native.
What’s up with Java in HFT stuff then? I’ve never understood this: from what I understand in order for it to work, you have to intentionally avoid doing many allocations, and that seems like you’ll be throwing massive amounts of the ecosystem (Javas biggest strength) away.
- kaba0 4y agoThey should not allocate on the hot path/after the initial set up, which is much more manageable. Old objects are not a problem for generational GCs.