Go performance from version 1.2 to 1.18

Re:Go performance from version 1.2 to 1.18 by kryptiskt on Friday February 04, 2022 @04:20AM (#30204578)

> Sorry, I think you have the wrong idea. A VM, is an implementation detail that gets carried to the execution. A VM is the runtime that runs on top of the original runtime(tm) that is the OS. A Go / C program will run directly on the OS. Adding a layer of runtime means reduced performance.

After the bytecode has been JIT compiled it runs as close to the metal as a Go program. If you want fast startup you can even compile the code ahead of time and there is absolutely no difference. Apart from .NET not insisting on its own calling convention, which means it has far less overhead when interacting with external libraries than Go.

[ Parent | on HN ]

Re:Go performance from version 1.2 to 1.18 by VBprogrammer on Friday February 04, 2022 @06:04AM (#30205311)

This whole thread is childish and pointless. Literally 14 year old me would have recognised these arguments and relished getting stuck into them.

I've seen a stack built almost entirely in TCL which handled 10,000 transactions per second for a FTSE 100 company. If that's possible then language is just one choice in the infinite possibilities of production stacks.

[ Parent | on HN ]