How does enClose handle performance optimization and memory management when bridging between native Swift code and JavaScript in high-frequency interaction scenarios?

> Unlike traditional hybrid frameworks with predefined APIs or plugin systems, enClose removes restrictions, giving developers complete freedom to build any app they envision.

> Unlike Cordova, which can be limiting and complex, enClose offers a refreshing alternative. It doesn't confine you to a predefined set of functions via an API; instead, it enables you to tap into the full potential of the iOS and MacOS platforms.

The fact that a GitHub repo's readme is full of vague terms, zero examples, use cases and technical details just feels awfully distressing to me. It's a marketing pitch, sure there's no harm in it but feels like the wrong place for it.