What if we want to shut down once a certain number of subtasks have succeeded-say, after 1,000 tasks have successfully completed-rather than waiting for all of them? Is there a mechanism within structured concurrency to handle this scenario?
Actually, there's kind of goto in java outerLoop: for (int i = 0; i < 10; i++) { for (int j = 0; j < 10; j++) { if (someCondition) { break outerLoop; // This breaks out of both loops } } }
Project Reactor? Like RxJava? Reactive programming as a paradigm doesnt scale all that well and leads to confusing code. There's a reason it didnt take off. Developers like imperative programming style. Think of this as similar to Kotlins coroutines.
![Blox Fruits Dragon Rework Update [Full Stream]](http://i.ytimg.com/vi/EqDAp8udhm0/mqdefault.jpg)
"Scheduling runnables is like goto" love this!
it's so relaxing listening to him
Great talk, i did not think in the debug part, amazing
What if we want to shut down once a certain number of subtasks have succeeded-say, after 1,000 tasks have successfully completed-rather than waiting for all of them? Is there a mechanism within structured concurrency to handle this scenario?
Actually, there's kind of goto in java
outerLoop:
for (int i = 0; i < 10; i++) {
for (int j = 0; j < 10; j++) {
if (someCondition) {
break outerLoop; // This breaks out of both loops
}
}
}
so it's like coroutines then ?!
I need another person explaining this other than this lady.
This is terrible api, seriously. Reactor implemented all that functionality a while ago in a much better way.
Project Reactor? Like RxJava? Reactive programming as a paradigm doesnt scale all that well and leads to confusing code. There's a reason it didnt take off. Developers like imperative programming style. Think of this as similar to Kotlins coroutines.
Continuations has the massive benefit of not coloring functions. This is not the case with the Reactive or Flow (or futures or suspend)
@@sandrodelacruz8125this is better than Kotlin's coroutines in that it doesn't color functions