Does Jule's reference counting reclaim reference cycles in long-running services?
Jule compiles through C++ to a self-contained native binary and manages heap memory with automatic reference counting, giving deterministic destruction without a tracing collector. For a long-running, low-traffic service where resident memory should stay small, that model looks attractive, but it leaves one behavior unresolved around cyclic data. Reference c
jule