I can neither confirm, nor deny that I am in fact D̵̡̮̻̗̖̮͔̜͈̙͖͙͍̺̀̒̍̌̑͐̓͡å̴̲͍̋̉́̀̑͊̎̐̊͡l̴̟̭̳̄̅̕͝͠͝ȩ̸͚̼̘̫̺̻̬̻̮͖̣̬̖̠̗̎̌ ̵̯͕͛́͋͌̀͝͠ͅͅG̷̛͈̩̟̟̠͓̗̘͓͍̽̒̌̔̓̈͗̐̈̿͠͠r̷̘̞̹͂̀̑̋̀͌̍͗̆͝͠͝ͅi̶̡͔͖͍̟̲̮͑̎͌̀̎b̵̡̢̹̗͔̗͍̘̣͊͊̑͒̍̑͌̽͋͌̔͝͝b̷̭̩̩̣͙̺͎̱̗͙͚̩̈́l̸̛͎̼̟̋͆͆͗̓̓̓͘͟ĺ̶̼͇͎̫̮͎̣̳͉̯̊̆̂̓̄̍̃̚e̶̢̡̛̫̣͈̺̾̅͐̾̓͒̚ͅ.̴̫̞̥̒̈̇̓́̾͗̒́̉̔͑
I personally love Rust, but since I’m already familiar with C/CMake, I just don’t think I need to “re-invent the wheel”. In this case, using the Rust wrapper option is more like “trying to put a winter tire around an all-weather tire”.
- libsnorble-2-dev, a C library that the author only distributes as source code and therefore must be compiled from source using CMake
Of the available options, this is easily the best since I can use my own compilation flags to tune the library for my specific target architecture/CPU which can possibly change as the deployment profile for the business case evolves. Assuming it’s OSS, I can also fork and adjust the library itself for said “mission-critical” use case.
Also, the Google product being deprecated since '17 is too real 😅…
Making fun of people has more “stank” in English (not a hard fact, just my opinion).