documentation VS kernel-wasm

The example from the PureScript documentation is:

Filippo: With Haskell knowledge, reading PureScript documentation was enough.

See https://github.com/purescript/documentation/blob/master/errors/TypesDoNotUnify.md for more information, or to contribute content related to this error.

[1 of 1] Compiling Main Error found: in module Main at src/Main.purs:40:35 - 40:39 (line 40, column 35 - line 40, column 39) Could not match type { age :: Maybe Int , name :: String , team :: Maybe String} with type Json while checking that type t0 is at least as general as type Json while checking that expression user has type Json in value declaration main where t0 is an unknown type See https://github.com/purescript/documentation/blob/master/errors/TypesDoNotUnify.md for more information, or to contribute content related to this error. [error] Failed to build.)

I'm trying to get a better grasp on the type system of purescript. One thing I'm struggling to fully understand is how the so-called "kind system" works. The language reference is very brief about it.

purescript uses (_ - 5) for that operator section, which i'm not a total fan of, but it's at least unambiguous; agda would write it as _- 5

The one page you should add to the documentation is "differences from Vim".

For example, https://github.com/purescript/documentation/blob/master/lang... makes picking up PureScript as a Haskell programmer much easier than having to read all of the documentation and do the diff yourself.

More info can be found here: https://github.com/purescript/documentation/blob/master/guides/Getting-Started.md

WASM is not related to JavaScript in any way, it's just a formal definition (see the spec) for a bytecode and a VM that executes it. One of the problems that WASM tries to solve for web development is to get away from JS because it's such a mess. It's unfortunate that WASM has "Web" in its name, as it's rally not just for Web: there are many embedded runtimes, for example, popular proxy server Envoy supports WASM for writing filters (aka extensions) and there's even WASM runtime for the Linux kernel.

Wasm started in the web, but has since been ported even to the Linux kernel [0]. It seems perfect for situation where you near machine code levels of performance, but don't want to carry different binaries for different CPU architectures - exactly what you want from a plugin system. It also allows far greater isolation than "real" compiled code.

[0] https://github.com/wasmerio/kernel-wasm