Difference between revisions of "The JavaScript Problem"

From HaskellWiki
Jump to navigation Jump to search
m (typos)
(10 intermediate revisions by 4 users not shown)
Line 3: Line 3:
 
The JavaScript problem is two-fold and can be described thus:
  
The JavaScript problem is two-fold and can be described thus:
   
−
# '''JavaScript sucks.''' The depths to which JavaScript sucks is well-documented and well-understood. Its main faults are: its lack of module system, weak-typing, verbose function syntax¹, late binding², which has led to the creation of various static analysis tools to alleviate this language flaw³, but with limited success⁴ (there is even a static type checker⁵), finicky equality/automatic conversion, <code>this</code> behaviour, and lack of static types. Coffeescript is the most mainstream javascript alternative. Although it makes many aspects of Javascript sane and convenient, it still suffers from weak-typing.
 +
# '''JavaScript sucks.''' The depths to which JavaScript sucks is well-documented and well-understood. Its main faults are: its lack of module system, weak-typing, verbose function syntax¹, late binding², which has led to the creation of various static analysis tools to alleviate this language flaw³, but with limited success⁴ (there is even a static type checker⁵), finicky equality/automatic conversion, <code>this</code> behaviour, and lack of static types.
  +
−
#:
  
 
# '''We need JavaScript.''' Using it for what it is good for, i.e. providing a platform for browser development, but not using the language ''per se'', is therefore desirable, and many are working to achieve this, in varying forms. There are various ways to do it, but we ought to opt for compiling an existing language, Haskell, to JavaScript, because we do not have time to learn or teach other people a new language, garner a new library set and a new type checker and all that Haskell implementations provide.
  
# '''We need JavaScript.''' Using it for what it is good for, i.e. providing a platform for browser development, but not using the language ''per se'', is therefore desirable, and many are working to achieve this, in varying forms. There are various ways to do it, but we ought to opt for compiling an existing language, Haskell, to JavaScript, because we do not have time to learn or teach other people a new language, garner a new library set and a new type checker and all that Haskell implementations provide.
   
−
== Updating this page ==
 +
== Mainstream alternatives ==
  +
  +
=== Coffeescript ===
  +
It makes many aspects of Javascript sane and convenient, and you get a compilation check that verifies syntax, however it still suffers greatly from weak-typing.
  +
  ⚫
=== TypeScript ===
  +
  +
Structural typing with traditional generics on top of Javascript.
  +
Of all the alternatvies, TypeScript's advantage is that it makes no changes to Javascript. Existing javascript code that passes jshint is valid Typescript code. TypeScript also adds features from the latest javascript standards that it can compile down to older versions of javascript. TypeScript is by far the easiest javascript variant to learn. The downside is that one might desire a better language then just javascript + types.
  +
  +
TypeScript defaults to dynamic typing when it can't figure the type out. However, it now has a noImplicitAny setting that will give a compilation error if it can't figure out the type.
   
  +
Structural sub-typing seems a good fit for JavaScript.
−
Please update and expand this page with the various attacks on this problem and their progress. The question of The JavaScript Problem comes up every so often and this should be the page to link people to.
  
  +
Perhaps Typescript's biggest problem is that null is a valid value for any type.
   
−
== Attacks ==
 +
== Haskell -> JS ==
   
 
=== UHC ===
  
=== UHC ===
   
−
Original blog post [https://github.com/atzedijkstra/javascript-runtime-for-UHC here.] Quickstart guide [http://chrisdone.com/posts/2012-01-06-uhc-javascript.html here.] A more in-depth discussion about the current capabilities of the backend [http://www.norm2782.com/improving-uhc-js-report.pdf here.] Blog post of using UHC in a real app [http://alessandrovermeulen.me/2012/01/26/getting-rid-of-javascript-with-haskell/ here.]
 +
Original blog post [https://github.com/atzedijkstra/javascript-runtime-for-UHC here.] Quickstart guide [http://chrisdone.com/posts/2012-01-06-uhc-javascript.html here.] A more in-depth discussion about the current capabilities of the backend [http://www.norm2782.com/improving-uhc-js-report.pdf here.] For an example of using the JavaScript compilation for a real app see this [http://alessandrovermeulen.me/2012/01/26/getting-rid-of-javascript-with-haskell/ blog post], there is also a port of wxAsteroids to the browser (see [http://uu-computerscience.github.io/js-asteroids/ github] or a [http://www.rubendegooijer.nl/posts/2013-04-06-haskell-oop.html blog post]).
   
 
* Beta.
  
* Beta.
Line 45: Line 56:
 
=== Haste ===
  
=== Haste ===
   
  +
[http://haste-lang.org Website], [http://hackage.haskell.org/package/haste-compiler Hackage]
−
[https://github.com/valderman/haste-compiler Haste on GitHub], [https://github.com/valderman/glosie/tree/hsglosie example application], [http://ekblad.cc/hastereport.pdf thesis paper].
  
   
  +
* Seamless, type-safe single program framework for client-server communication
−
* Work in progress.
  
  +
* Easy Javascript interoperability
−
* Generates relatively small code (in general between 0.9 and 5 times the size of functionally equivalent JS).
  
  +
* Generates small, fast, minifiable code.
−
* Also generates relatively fast code (run times in general between 0.9 and 8 times that of functionally equivalent JS).
  
  +
* Lightweight concurrency, Cabal integration, FFI and GHC extensions supported.
  +
* Cross platform.
 
* Works.
  
* Works.
−
* Very simple runtime.
  
−
* Accompanying FRP and very basic DOM libraries.
  
−
* Calling back into JS via FFI is supported.
  
−
* (Supposed to be) relatively easy to install and use.
  
   
 
=== [[JMacro]] ===
  
=== [[JMacro]] ===
Line 60: Line 69:
 
On the Haskell wiki (see above) and on [http://hackage.haskell.org/package/jmacro hackage]
  
On the Haskell wiki (see above) and on [http://hackage.haskell.org/package/jmacro hackage]
   
−
* Mature
 +
* Mature, Maintained
  +
* Not Haskell but an EDSL _in_ Haskell nonetheless.
−
* Works
  
  +
* JMacro Panels provides a purely haskell combinator library that generates dynamically updating html and js with asynchronous client-server communication.
−
* Complete
  
−
* Maintained
  
−
* Not Haskell
  
 
* Syntax is a fusion of Haskell and JavaScript
  
* Syntax is a fusion of Haskell and JavaScript
 
* Untyped, but with syntactic correctness (at least) enforced at compile-time.
  
* Untyped, but with syntactic correctness (at least) enforced at compile-time.
Line 70: Line 77:
 
* Support for various forms of code-generation
  
* Support for various forms of code-generation
   
−
=== Roy ===
 +
=== Others ===
   
  ⚫
* [https://github.com/johang88/haskellinjavascript Haskell interpreter in JS] — An interpreter. Haven't tried but is apparently dead.
⚫
[http://roy.brianmckenna.org/ Roy]: meld JavaScript semantics with functional languages. Experimental, but has many bread-and-butter Haskell features. Probably does not generate efficient code.
  
  ⚫
* YHC JS backend — Beta-ish. Apparently works, but I was unable to compile YHC, so haven't tried yet. I would be interested in anyone's experience using it. There's [http://www.haskell.org/haskellwiki/Yhc/Javascript an old wiki page] about Yhc's JavaScript support, but Yhc itself is a dead project.
  ⚫
* Emscripten — not Haskell→JS, but compiles LLVM/Clang output to JavaScript. Could possibly be used for GHC→LLVM→JS compiling, which I tried, and works, but would have to also compile the GHC runtime which is not straight-forward (to me) for it to actually run.
  ⚫
* hjscript — Beta. EDSL, not Haskell→JS. Works. Not ''very'' annoying to program in, but is JS semantics, not Haskell. Hackage package [http://hackage.haskell.org/package/HJScript here.]
  ⚫
* Some have also tried writing a Haskell→JS compiler to make a more direct JS-aware translation of code (to not have huge code output a la GHCJS, YHC, Emscripten).
  +
  +
  +
== FP -> JS ==
  +
  +
=== Ur/Web ===
  +
  +
http://www.impredicative.com/ur/
  +
  +
Perhaps the problem with Ur is that they are selling both a backend and a frontend together. Being a new language, the backend is lacking in libraries to be practical for many tasks. However, there is an RSS reader that is using Ur for the front-end and Haskell for the backend: https://bazqux.com/
  +
  +
  +
=== OCaml ===
  +
  +
The OCaml -> JS compiler is supposed to be good, it is now used at facebook for an internal in-browser code editor.
  +
http://ocsigen.org/js_of_ocaml/
  +
  +
=== GorrilaScript ===
  +
  +
http://ckknight.github.io/gorillascript/
  +
  +
immutable by default, global type inference, macros, what coffeescript should have been. The syntax is similar to coffeescript
  +
  +
=== Roy, PureScript ===
  +
  ⚫
[http://roy.brianmckenna.org/ Roy]: meld JavaScript semantics with functional languages. Experimental, but has many bread-and-butter Haskell features.
  +
Roy is written in JS. PureScript is written in Haskell.
   
 
=== Idris ===
  
=== Idris ===
Line 96: Line 133:
 
* [http://en.wikipedia.org/wiki/Dependent_type WP (en) Dependent type] (with Idris listed under language comparison)
  
* [http://en.wikipedia.org/wiki/Dependent_type WP (en) Dependent type] (with Idris listed under language comparison)
   
⚫
=== Others ===
  
−  
⚫
* [https://github.com/johang88/haskellinjavascript Haskell interpreter in JS] — An interpreter. Haven't tried but is apparently dead.
  
⚫
* YHC JS backend — Beta-ish. Apparently works, but I was unable to compile YHC, so haven't tried yet. I would be interested in anyone's experience using it. There's [http://www.haskell.org/haskellwiki/Yhc/Javascript an old wiki page] about Yhc's JavaScript support, but Yhc itself is a dead project.
  
⚫
* Emscripten — not Haskell→JS, but compiles LLVM/Clang output to JavaScript. Could possibly be used for GHC→LLVM→JS compiling, which I tried, and works, but would have to also compile the GHC runtime which is not straight-forward (to me) for it to actually run.
 
⚫
* hjscript — Beta. EDSL, not Haskell→JS. Works. Not ''very'' annoying to program in, but is JS semantics, not Haskell. Hackage package [http://hackage.haskell.org/package/HJScript here.]
  
⚫
* Some have also tried writing a Haskell→JS compiler to make a more direct JS-aware translation of code (to not have huge code output a la GHCJS, YHC, Emscripten), but ought to prefer to avoid NIH and hack on GHCJS or UHC.
  
   
 
== Links ==
  
== Links ==

Revision as of 12:47, 1 April 2014

The problem

The JavaScript problem is two-fold and can be described thus:

  1. JavaScript sucks. The depths to which JavaScript sucks is well-documented and well-understood. Its main faults are: its lack of module system, weak-typing, verbose function syntax¹, late binding², which has led to the creation of various static analysis tools to alleviate this language flaw³, but with limited success⁴ (there is even a static type checker⁵), finicky equality/automatic conversion, this behaviour, and lack of static types.
  1. We need JavaScript. Using it for what it is good for, i.e. providing a platform for browser development, but not using the language per se, is therefore desirable, and many are working to achieve this, in varying forms. There are various ways to do it, but we ought to opt for compiling an existing language, Haskell, to JavaScript, because we do not have time to learn or teach other people a new language, garner a new library set and a new type checker and all that Haskell implementations provide.

Mainstream alternatives

Coffeescript

It makes many aspects of Javascript sane and convenient, and you get a compilation check that verifies syntax, however it still suffers greatly from weak-typing.

TypeScript

Structural typing with traditional generics on top of Javascript. Of all the alternatvies, TypeScript's advantage is that it makes no changes to Javascript. Existing javascript code that passes jshint is valid Typescript code. TypeScript also adds features from the latest javascript standards that it can compile down to older versions of javascript. TypeScript is by far the easiest javascript variant to learn. The downside is that one might desire a better language then just javascript + types.

TypeScript defaults to dynamic typing when it can't figure the type out. However, it now has a noImplicitAny setting that will give a compilation error if it can't figure out the type.

Structural sub-typing seems a good fit for JavaScript. Perhaps Typescript's biggest problem is that null is a valid value for any type.

Haskell -> JS

UHC

Original blog post here. Quickstart guide here. A more in-depth discussion about the current capabilities of the backend here. For an example of using the JavaScript compilation for a real app see this blog post, there is also a port of wxAsteroids to the browser (see github or a blog post).

  • Beta.
  • Only works for UHC, but promising.
  • UHC compiles enough of Hackage to be very useful.
  • Doesn't produce an explosion of code, seemingly.
  • Fairly substantial JS/DOM/W3C/HTML5 API.
  • Currently works.

Fay

Website: http://fay-lang.org/ Discussion on Reddit: Fay slides. The package is on Hackage. Fetch with Git: 

 git clone git://github.com/faylang/fay.git
  • Compiles a subset of Haskell, needs more
  • Currently works.

GHCJS

The Github page is here.

  • Alpha.
  • Works.
  • Incomplete.
  • Nicely designed.
  • Compiles most pure Haskell libraries no problem.
  • FFI to JS works, and the author, sviperll is a helpful guy.

Haste

Website, Hackage

  • Seamless, type-safe single program framework for client-server communication
  • Easy Javascript interoperability
  • Generates small, fast, minifiable code.
  • Lightweight concurrency, Cabal integration, FFI and GHC extensions supported.
  • Cross platform.
  • Works.

JMacro

On the Haskell wiki (see above) and on hackage

  • Mature, Maintained
  • Not Haskell but an EDSL _in_ Haskell nonetheless.
  • JMacro Panels provides a purely haskell combinator library that generates dynamically updating html and js with asynchronous client-server communication.
  • Syntax is a fusion of Haskell and JavaScript
  • Untyped, but with syntactic correctness (at least) enforced at compile-time.
  • Embeddable through quasi-quoting
  • Support for various forms of code-generation

Others

  • Haskell interpreter in JS — An interpreter. Haven't tried but is apparently dead.
  • YHC JS backend — Beta-ish. Apparently works, but I was unable to compile YHC, so haven't tried yet. I would be interested in anyone's experience using it. There's an old wiki page about Yhc's JavaScript support, but Yhc itself is a dead project.
  • Emscripten — not Haskell→JS, but compiles LLVM/Clang output to JavaScript. Could possibly be used for GHC→LLVM→JS compiling, which I tried, and works, but would have to also compile the GHC runtime which is not straight-forward (to me) for it to actually run.
  • hjscript — Beta. EDSL, not Haskell→JS. Works. Not very annoying to program in, but is JS semantics, not Haskell. Hackage package here.
  • Some have also tried writing a Haskell→JS compiler to make a more direct JS-aware translation of code (to not have huge code output a la GHCJS, YHC, Emscripten).


FP -> JS

Ur/Web

http://www.impredicative.com/ur/

Perhaps the problem with Ur is that they are selling both a backend and a frontend together. Being a new language, the backend is lacking in libraries to be practical for many tasks. However, there is an RSS reader that is using Ur for the front-end and Haskell for the backend: https://bazqux.com/


OCaml

The OCaml -> JS compiler is supposed to be good, it is now used at facebook for an internal in-browser code editor. http://ocsigen.org/js_of_ocaml/

GorrilaScript

http://ckknight.github.io/gorillascript/

immutable by default, global type inference, macros, what coffeescript should have been. The syntax is similar to coffeescript

Roy, PureScript

Roy: meld JavaScript semantics with functional languages. Experimental, but has many bread-and-butter Haskell features. Roy is written in JS. PureScript is written in Haskell.

Idris

Idris is a compiled language with dependent types, implemented in Haskell, with backends for both LLVM and JavaScript. Experimental.

  • Full dependent types with dependent pattern matching where clauses, with rule, simple case expressions, pattern matching let and lambda bindings
  • Dependent records with projection and update
  • Type classes
  • Monad comprehensions
  • Syntactic conveniences for lists, tuples, dependent pairs do notation and idiom brackets
  • Indentation significant syntax
  • Extensible syntax
  • Tactic based theorem proving (influenced by Coq)
  • Cumulative universes
  • Totality checking
  • Simple foreign function interface (to C)
  • Hugs style interactive environment

Links:


Links

Footnotes

  1. Its support for closures is commonly noted as being one of JavaScript’s redeeming features.
  2. Early binding allows for static verification of the existence of method-signature pairs (e.g. v-tables). Late binding does not give the compiler (or an IDE) enough information for existence verification, it has to be looked up at run-time.
  3. There are several hinting libraries, which developers insist are indispensable tools when developing JavaScript seriously, such as JavaScript lint, JSLint, and JSure.
  4. “Any non-trivial analysis is very difficult due to Javascript’s dynamic nature.” — Berke Durak, Ph.D., author of jsure.
  5. Google Inc. thought it necessary to develop a compiler, Google Closure, which does type-checking and limited inference.
Retrieved from "https://wiki.haskell.org/index.php?title=The_JavaScript_Problem&oldid=57727"