ESP8266_RTOS_SDK VS zig

I was using the ESP8266 RTOS SDK (https://github.com/espressif/ESP8266_RTOS_SDK) and using the smartconfig example (https://github.com/espressif/ESP8266_RTOS_SDK/tree/master/examples/wifi/smart_config) with my iOS app. On the mobile side, I was using the EspressifTouchSDK 1.1.0 (https://github.com/EspressifApp/EsptouchForIOS). Basic need was to transfer WiFi SSID - Password to the Esp from the mobile and smartconfig achieved this fast & easy without hassle.

Imagine my disappointment after working on a statically allocated HTTP server stack to discover that even `esp_log.h` does several malloc() calls [1] per log output line... thankfully that was only on the ESP8266_RTOS_SDK, and esp-idf isn't quite as bad.

[1] https://github.com/espressif/ESP8266_RTOS_SDK/blob/89a3f254b...

Maybe this is what they are referring to: https://github.com/espressif/ESP8266_RTOS_SDK/tree/d47d527e0502595700db7b8c468a691c537f6d0b/examples/wifi/smart_config

Don't all legal documents do? I am not a lawyer of any sort (tho have worked with typing things for a firm) and I tried my best, using an example from this

1) The first one is the ESP8266 rtos sdk ( https://github.com/espressif/ESP8266_RTOS_SDK ) I wouldnt recommend this approach for you, as you already work with an Arduino libraries. So with the bare esp8266 rtos sdk you have to do more to achieve your goal.

Some general ESP8266 RTOS examples here: https://github.com/espressif/ESP8266_RTOS_SDK/tree/master/examples

There is an issue proposing this approach: https://github.com/ziglang/zig/issues/4284

https://github.com/ziglang/zig/issues/224

e.g.:

> > When debugging/prototyping, it's useful to comment out a line without having to refactor, e.g.

When writing code in a scripting language, sometimes you need that extra bit of performance (or maybe an async feature from Zig).

NodeJS is by no means a slow runtime, it wouldn’t be so popular if it was. But compared to Bun, it’s slow. Bun was built from the ground up with speed in mind, using both JavascriptCore and Zig. The Bun team spent an enormous amount of time and energy trying to make Bun fast, including lots of profiling, benchmarking, and optimizations.

ntdll.dll!RtlUserThreadStart()

There are valid reasons to use APIs from NTDLL. Where I disagree with zig#1840 is the idea that it is always better to use NTDLL versions of API. Every other software ecosystem uses the standard Win32 APIs and diverging from that without a good reason seems like a good way to have unexpected behavior. One concrete example is most users and programmers expect Windows to redirect some file system paths when running on WOW64. But this is implemented in Kernel32, not ntdll.

https://github.com/ziglang/zig/issues/11894

Zig also has an IRC channel on libera (#zig) that is moderated by Andrew Kelley.[1]

[1] https://github.com/ziglang/zig/wiki/Community