Advantage of this repo over azure-sdk-for-c ?

[KammutierSpule]

Is there an existing issue for this?

• I have searched the existing issues

Version

main

Description of the issue

I'm evaluating to using this repository over https://github.com/Azure/azure-sdk-for-c to be used on ESP32.
I read the https://github.com/Azure/azure-iot-middleware-freertos/blob/main/docs/azure_iot_c_sdk_port.md
However it is still not clear that would be the benefits.

Specially, I was looking for split the application layer from the (OS and HW) target and using this repository, it will create a direct dependency of FreeRTOS.

I understand there may be helpfully code here, but on this case it could be useful for other targets than FreeRTOS too.

Looking at https://github.com/Azure/azure-sdk-for-c sample, they look simpler and only need to wrap MQTT functions.

What should I consider while using this repository or azure-sdk-for-c ?

Related: #324

Expected behavior

No response

Steps to reproduce the issue

No response

Relevant log output

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[rtheil-growlink]

Smaller memory footprint. Full control over memory allocation (this library is non-allocating). I find it has lower latency and faster connect times than sdk-for-c, but this is based on that repo.