Starting threads is very expensive, although acceptable for now to help with JDA's thread-blocking methods. However, using pools with workers would be way better.
Starting threads is very expensive, although acceptable for now to help with JDA's thread-blocking methods. However, using pools with workers would be way better.
[Useful Link](https://www.javatpoint.com/java-thread-pool)
bea
added the enhancement label 2022-11-22 22:34:21 +01:00
Also look into: Executors.newScheduledThreadPool(), but this might be more useful for the scheduled tasks (as the name suggests) like expired messages, trivia, heartbeat...
Also look into: `Executors.newScheduledThreadPool()`, but this might be more useful for the scheduled tasks (as the name suggests) like expired messages, trivia, heartbeat...
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Starting threads is very expensive, although acceptable for now to help with JDA's thread-blocking methods. However, using pools with workers would be way better.
Useful Link
Also look into:
Executors.newScheduledThreadPool(), but this might be more useful for the scheduled tasks (as the name suggests) like expired messages, trivia, heartbeat...