3 ms·
There are both memory and performance considerations. For a server/db web application this may not be a problem, but for e.g. some logic in a game engine that r
by alkonaut 11y ago
There are both memory and performance considerations. For a server/db web application this may not be a problem, but for e.g. some logic in a game engine that runs every frame on a mobile device, then using 16 extra locks per map for example isn't a good idea. Nor is having 5% performance overhead.
I can agree with an argument that thread-safe should be default and specialized/fast collections should be optional though.
- astrafoo 11y agoPeople who care about 5% performance overhead will never use Go in the first place.
- alkonaut 11y agoThat's just not true. Regardless of language there is always a portion of the code where you need to be careful with performance. I have spent endless hours tweaking map performance in .NET, for example.