Rayon should not be a default feature.

[oligamiq]

What can be improved or is missing?

Rayon should not be a default feature.

Implementation Approach

Please use feature about rayon.

Pull Request

#241

[johannesvollmer]

Yes, I agree :)

Just because I'm curious, what's it you're trying to do, where rayon must be disabled?

[oligamiq]

image_rs depends on Rayon by default. The number of dependency libraries in the software I am currently developing has reached 227, and many of the libraries I am using directly rely on image_rs, which in turn depends on Rayon. Therefore, I have started working to ensure that image_rs will no longer depend on Rayon within the next six months.

[johannesvollmer]

Are there problems in particular with rayon, or do you simply want to reduce dependencies?

[oligamiq]

As far as I know, rayon creates threads according to the number of cores and then begins execution using virtual threads. This is the same approach as Go and is very well designed for using all resources efficiently. However, since it's not implemented at the language level, if you create your own threads, you'll end up generating more threads than the number of cores, which will likely reduce efficiency. Also, the software I'm developing is intended to run continuously in real-time on devices like laptops, so I do create my own threads. More importantly, I don't want all the cores to be fully consumed, even if only for a moment.
Additionally, I would like to reduce the number of dependencies.

[dgsantana]

One option is to reduce the number of thread of rayon to 1, you can do that with this.

[oligamiq]

Thank you. So that's another way to do it.

[johannesvollmer]

Good to know, thanks :) Still I think we should allow people to opt out of the rayon dependency. If you are still interested in doing that, of course.

[oligamiq]

Me too.