Alex Nedelcu on Nostr: npub1yy8jn…vyfzq You may be right, but Future was also liked because the API was ...
npub1yy8jnmvkegndrlygssm979wf04jema23uc3384fu8nklacxfqyas5vyfzq (npub1yy8…yfzq) You may be right, but Future was also liked because the API was nice (e.g., flatMap, sequence), even if it was more error-prone. And the trouble with Java's thread-pools is that they are often limited, so blocking threads is error-prone. And Future did not have the performance of Cats-Effect IO.
Java could've had one thread-pool, like System.Threading.ThreadPool from dotNET. Probably bad idea for constrained devices (Android), but not for server-side.
Java could've had one thread-pool, like System.Threading.ThreadPool from dotNET. Probably bad idea for constrained devices (Android), but not for server-side.