: Removal or disabling of legacy Flash components.
Before diving into the specifics of 2.5.0, let’s establish a baseline. AIO Runtimes (All-in-One Runtimes) are lightweight, multi-threaded execution environments designed to run compiled bytecode or interpreted scripts without a host OS overhead. Unlike traditional runtimes (e.g., Node.js, Python, or JVM), AIO Runtimes are built on three core principles: aio runtimes 2.5.0
If you're an existing user of aio-runtimes, upgrading to version 2.5.0 is a straightforward process. The aio-runtimes project provides detailed documentation and migration guides to help you upgrade your applications to the latest version. : Removal or disabling of legacy Flash components
| Feature | 2.4.x behavior | 2.5.0 behavior | | :--- | :--- | :--- | | aio_task_yield() | Always reschedules at queue tail. | May migrate to a different core if current core is overloaded. | | File watch API | Callback receives (path, event_mask) . | Callback receives a struct AioFileEvent with timestamp and cookie. | | Build system | CMake only. | CMake + Zig build (for cross-compilation). Legacy CMake scripts need updating. | | TLS (Thread Local Storage) | Limited to 4 slots. | 64 slots, dynamic allocation. But offsets changed; recompile required. | Unlike traditional runtimes (e