> Controversial opinion (?): on your code hot paths and bottlenecks (and only there), where performance really matters (don't guess where they are, but measure with proper benchmarks) strive to avoid using Java Stream API, even at cost of more verbosity and/or less readability.<p>An example would be useful.