> Go doesn't belong in this discussion.its a better java, c#, python and not much more. It doesn't work for 24/7 or for performance sensitive applications.
The claim is factually backwards. Go significantly outperforms Java, C#, and Python (~10x faster than Python, lower memory usage than C#), and runs successfully in countless 24/7 production systems including high-throughput APIs and distributed services.
The actual valid concern, which made me question its suitability, is that Go wouldn't be appropriate for TigerBeetle's specific real-time requirements. TigerBeetle is a financial transaction database requiring deterministic, predictable microsecond-level latencies with strict timestamp ordering across a distributed consensus protocol. Go's garbage collector introduces unpredictable pauses that would likely violate these hard real-time guarantees.
The claim is factually backwards. Go significantly outperforms Java, C#, and Python (~10x faster than Python, lower memory usage than C#), and runs successfully in countless 24/7 production systems including high-throughput APIs and distributed services.
The actual valid concern, which made me question its suitability, is that Go wouldn't be appropriate for TigerBeetle's specific real-time requirements. TigerBeetle is a financial transaction database requiring deterministic, predictable microsecond-level latencies with strict timestamp ordering across a distributed consensus protocol. Go's garbage collector introduces unpredictable pauses that would likely violate these hard real-time guarantees.