fuego

The README admits that several operations may be memory intensive or poorly performing, and Go's type parameter issues can lead to performance hits, limiting scalability.

Due to Go's lack of parameterised methods, users must use verbose casting functions like C and CC, resulting in leftward-growing code chains that obscure intent, as explained in known limitations.

Concurrent processing is not supported across all Stream methods, and users must manage distribution manually, making it less seamless for advanced parallel workflows.

Marked as a research project with breaking changes between major versions, it lacks the stability expected for critical production systems, requiring cautious adoption.