A general problem with interlanguage benchmarks is that you can only compare those features that both languages have, so these always reduce to lowest common denominator and are inherently biased against new features. So for example, go will get no credit for having a garbage collector, checked array and string indexing operations, maps, slices, type assertions, interfaces, reflection, channels, resizeable stacks, etc.
On Sunday, February 3, 2019 at 7:15:36 PM UTC-5, Miki Tebeka wrote: > > Thanks. You're right - this is not the way to choose a language. I was > just curious. Go has many, many more things going for it - multi core > support, networking, standard library, community ... > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
