3 ms·
Meanwhile Java and .NET have had off-heap and arenas for a while now. Which goes to show how Go could be much better, if being designed with the learnings of o
by pjmlp 1y ago
Meanwhile Java and .NET have had off-heap and arenas for a while now.
Which goes to show how Go could be much better, if being designed with the learnings of others taken into account.
The adoption of runtime.KeepAlive() [0], and the related runtime.AddCleanup() as replacement for finalizers are also learnings from other languages [1].
[0] - https://learn.microsoft.com/en-us/dotnet/api/system.gc.keepalive?view=net-9.0 https://learn.microsoft.com/en-us/dotnet/api/system.gc.keepa...
[1] - https://openjdk.org/jeps/421 https://openjdk.org/jeps/421
- truth_seeker 1y agoWhat a coincedence ! :) Recently used MemorySegment in Java, it is extremely good. Just yesterday i implemented Map and List interface using MemorySegment as backing store for batch operations instead of using OpenHFT stuff. Tried -XX:TLABSize before but wasnt getting the deserved performance. Not sure about .NET though, havent used since last decade.