Dmitry

Here @sergeysova talking about effector in REDMADROBOT https://soundcloud.com/5minreact/063-effector 🇷🇺

There are purely practical issues: where do you plan to catch errors? `throw error` will fall literally into the void as application would have unit links of any depth: ```js...

There are three ways in which you might call fork, event and getState ([repl link](https://share.effector.dev/CrIzCAom)): 1) fork, get state, global call ```ts const scope = fork(root) console.log($store.getState(), scope.getState($store)) event() ```...

This idea imply that more information in `.watch` will follow, so I suggest api like that: ```ts createWatch({ unit, fn, scope, }: { unit: Unit fn: (value: T, options: {scopeName?:...

Seems reasonable 👍

For some reason, there is a major issue with scrolling: lack of "momentum" inertial scroll on iOS, which makes try effector almost unusable

Fixing an issue with inertial scroll caused an overscrolling: inability to see top 10 lines of code and UI above it after scrolling to the bottom

It was mostly incomplete and was removed

Looks like an issue in [effector-inspector](https://codesandbox.io/s/effector-logger-break-forked-irfksd?file=/src/App.js) If you set inspector option to true (which is a default) the issue occurs

In your case it's better to use imports from effector and _enable_ logger in development rather than disable it in production. In babel this looks like that: **.babelrc** ```json {...