The people bashing threads are typically system programmers which have in mind use cases that the typical application programmer will never encounter in her life.... In 99% of the use cases an application programmer is likely to run into, the simple pattern of spawning a bunch of independent threads and collecting the results in a queue is everything one needs to know.
"futures" --- objects representing the asynchronous execution of an operation. This powerful idea is the foundation not only of concurrent.futures but also of the asyncio packages.
end ...