| This applies to a lot of things unfortunately. There is a cult of just being afraid and scaring other people. "You can't do it, just use a library.". "Just use this library, everyone uses it.". "Even google uses this library, do you think you are better." etc. To add another example to this, you will read that memcpy is super mega optimized on libc and you shouldn't do it yourself etc. etc. etc. But if you just check clickhouse [1] as an example. They implemented it, it is pretty basic and they say it works well in the comments of the code. Also you can check musl libc code etc. and it is fairly simple. People still would argue that you used some intrinsic so it isn't portable or you just benchmarked on one case so it won't work well overall. Well you CAN benchmark as wide as you want inside your project and have a different memcpy code per project. This kind of thing isn't as bad as people make it out to be in my opinion. Ofc memcpy is just an example here and it applies similarly to memory allocation, io etc. As a negative note, imo this is one of the major reasons why most software is super crappy now. Everything uses some library -> those libraries change all the time -> more breaking -> more maintenance. Similar chain happens in terms of performance because the person that wrote that library probably doesn't even know how I am using the library. This is also why people have endless arguments about what library/tool to use while they can be learning more and more things every day. [1] https://github.com/ClickHouse/ClickHouse/blob/master/base/gl... |
Then you'll have a much better idea of when to _really_ use one that depends on intrinsics, is optimized etc, and how to benchmark them ... those are the real skills.