purescript / roadmap Goto Github PK

• Using PureScript without the core libraries
• How to write a code gen backend
• Setting up a development environment with pscid
• Using the new generics library
• Type driven development

PureScript is evolving at a rate at which bit rot in old blog posts can confound newcomers. Not only would it be nice to aggregate articles but perhaps request authors to gist their examples so we can automate testing.

This issue is to track things which we want to either move into core one day, or create with the intention of moving to core.

Existing Libraries

• purescript-jquery (needs some work first)

New Libraries

• Witherable
• Fast string parsing in the style of purescript-parser-generator
• Typed client/server communication (engine.io, perhaps)

Processing.js bindings; inspired by Quil.

Conveniences for handling JavaScript exceptions and Node thunks. Inspired by Result from the Swift community. Originally suggested by @archaeron in paf31/purescript-preface#1.

See purescript/purescript#780

This could take the form of a language specification together with #43.

Perhaps in the form of type-safe engine.io bindings on client and server.

PureScript takes a bit of manual work to get started with. Perhaps a Brunch plugin and skeleton could wrap other recommended tools like psa or psc-pane, Pulp, etc. Ideally it would seamlessly compile FFI with Babel or TypeScript too. Inspired by elm-brunch and elm-brunch-starter.

Not to be confused with the guidelines for writing libraries, but something more in the style of Elm's style guide or NoRedInk's Elm Style Guide.