Jump to content

Talk:PureScript: Difference between revisions

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
Content deleted Content added
Undid revision 888566010 by 77.185.75.42 (talk) remain AFD record for historical interest
No edit summary
Line 29: Line 29:
'''Future Directions'''
'''Future Directions'''
* Which aspects of the language are stable, which are in the progress of being extended & improved?
* Which aspects of the language are stable, which are in the progress of being extended & improved?
* Are there any essential design-principles that drive the evolution of the language? E.g. in C++ the motto is "you should not have to pay for what you don't use"... are there any similar philosophies in the evolution of PureScript?
* Are there any essential design-principles or philosophies that drive the evolution of the language? E.g. in C++, a central philosophy is "you should not have to pay for what you don't use"... are there any similar philosophies driving the evolution of PureScript?
* are there plans for standardization?
<!-- Template:Unsigned IP --><small class="autosigned">—&nbsp;Preceding [[Wikipedia:Signatures|unsigned]] comment added by [[Special:Contributions/77.185.75.42|77.185.75.42]] ([[User talk:77.185.75.42#top|talk]]) 23:42, 19 March 2019 (UTC)</small> <!--Autosigned by SineBot-->
<!-- Template:Unsigned IP --><small class="autosigned">—&nbsp;Preceding [[Wikipedia:Signatures|unsigned]] comment added by [[Special:Contributions/77.185.75.42|77.185.75.42]] ([[User talk:77.185.75.42#top|talk]]) 23:42, 19 March 2019 (UTC)</small> <!--Autosigned by SineBot-->

Revision as of 00:29, 20 March 2019


Proposed improvements:

Add the following sections:

Code examples

  • At least a "Hello World"
  • Maybe also a JavaScript FFI example, highlightling the ease of integration with existing JS-codebases/frameworks

Implementations

  • Mention alternative implementations, in particular purescript-native which targets C++ as a backend instead of EcmaScript.

Applications

  • Industry: There are already several companys which rely on PureScript for a significant portion of their codebase. A few of the major ones would be worth mentioning here, underlining the real-world significance and strength of PureScript.

Ecosystem

  • documentation on pursuit
  • Pulp
  • Bower
  • psc-package
  • Editor integrations (vscode, atom, vim/emacs)

Community

  • Maybe mention the discourse, github, slack channels, ...

Future Directions

  • Which aspects of the language are stable, which are in the progress of being extended & improved?
  • Are there any essential design-principles or philosophies that drive the evolution of the language? E.g. in C++, a central philosophy is "you should not have to pay for what you don't use"... are there any similar philosophies driving the evolution of PureScript?
  • are there plans for standardization?

— Preceding unsigned comment added by 77.185.75.42 (talk) 23:42, 19 March 2019 (UTC)[reply]