Cycle/DOM isolateModule is being bailed out be chrome profiler

[tusharmath]

version: 12.0.3

Dom driver performance suffers because of the try catch being used inside the loop.
https://github.com/cyclejs/cyclejs/blob/master/dom/src/isolateModule.ts#L26

Instead of using try/catch putting a simple if condition such as —

 if (!result.value) {
  hasNext = false
  break
}

Makes the driver perform much better. More details — GoogleChrome/devtools-docs#53

[wclr]

try catch in this case is really ugly
usage of try catch (along with setTimeout) should be regulated at least by the Supreme Court or even by International Court of Justice.

as well as usage for break and continue

[staltz]

Thank you @tusharmath
Sometimes my brain equals poop