Dmitry Iv.

After discussion with @stagas about [wat-compiler](https://github.com/stagas/wat-compiler) and [mono](https://github.com/stagas/mono) it became apparent that the right way to organize code is via compiled wasm files. ## 7. WASM binaries 👍🏼 Best possible...

Why? Node/browser support wasm frictionlessly

You won't believe but that's still work in progress. Once we rewrite fully to wasm we get it published. Stay tuned!

Nope, not this time. There's already https://github.com/orottier/web-audio-api-rs. We're coming up with something simpler - just direct wasms.

It is blocked, not abandoned. There's basically no resource for maintaining it. There's a couple of blockers need resolving first - audio-speaker implementation for node https://github.com/audiojs/audio-speaker/pull/44 and https://github.com/audiojs/audio-mpg123. You're welcome...

In webview it is impossible to get mic input, at least in iPhones, and also there might be trouble getting sound if the phone is in silent mode. In all...

There's an approach used by [escope](https://github.com/estools/escope), where there're no such environmental code in the source, the whole thing is written on ES6 and transpiled via babel to ES5 on deploy.

That is related to [classes-component](https://www.npmjs.com/package/classes-component) package in npm, which seems to be an older version of that component. The actual one is [component-classes](https://www.npmjs.com/package/component-classes). It might be a good idea to...

Yeah. The issue was with the dialog-component - it automatically tried to install the classes-component. It does not anymore.

```js // similar to settings-panel const params = [{ id: 'number', type: Number }] const params2 = { number: 3, ... } const [ fields, { set, submit, validate, reset...