2 ms·
On the contrary I think it is critical to compare them. You can then decide if the tradeoff is worth it for your use case. Even at a million tasks Go is still
by kevincox 3y ago
On the contrary I think it is critical to compare them. You can then decide if the tradeoff is worth it for your use case.
Even at a million tasks Go is still under 3 GiB of memory. So that is roughly 3KiB of memory overhead per task. That is likely negligible if your tasks are doing anything significant and most people don't need to worry about this number of tasks.
So this comparison shows that in many cases it is worth paying that price to avoid function colouring. But of course there are still some use cases where the price isn't worth it.