Onur Gündüz

**wearereasonablepeople** uses fp-ts too! * Homepage: [wearereasonablepeople.com](https://www.wearereasonablepeople.com/) * Logo: [Download](https://www.wearereasonablepeople.com/assets/img/logo_black.svg) * Open-source projects: Not yet available, but coming very soon.

So, if I am correct, this is an **in-browser** websockets implementation discussed in here. Perhaps, something like `node-inspector`? https://github.com/node-inspector/node-inspector/ And, how about some fancy ANSI graphics and so on? :)

Fancy graphics sounded like the logical next step after building sockets 👍 Thanks for also acknowledging that it's a plus by the way 😄 I will start with a React...

Commit https://github.com/francisrstokes/16bitjs/pull/54/commits/d92bec85dfb0f70c57bc66783496f5b2fde9c923 adds a simple test for encoding and decoding snapshots. I had to sandbox it using `vm` to prevent the changes from being permanent. Using `browserify` seemed very convenient...

Related: * https://github.com/microsoft/TypeScript/issues/29904 * https://github.com/microsoft/TypeScript/issues/30727 * https://github.com/unsplash/pipe-ts

```ts const resolve: (value: R) => fl.FutureInstance = fl.resolve ``` `L` is not parameterized in here, so it will always be `never`. ```ts const b = resolve_(42); // FutureInstance ```...