Developing Web Applications with Haskell • Hacker News Board

Re: Developing Web Applications with Haskell

#31

Post by tel » Sun, Jul 05, 2015, 6:12 PM UTC

dllthomas wrote: post #27

tel wrote: post #20

Earlier quoted context omitted.

There are a number of Haskell-to-JS compilers and Haskell-alike languages which more directly target JS. This is growing quickly but major issues remain and the toolkits are quite immature. On the other hand, much of React is a natural play out of Haskell's sweet spot. The challenge will be in making Js-alike APIs which handle the flexibility well while maintaining sufficient typing. React-like rendering, virtualdom,…

I recently had a great experience with GHCJS, although I wouldn't really say I'm using it in anger.

I find it pleasant every time I get something working in it... but significantly far away from anything I'd like to support in production. At least for now.

Re: Developing Web Applications with Haskell

#32

Post by tel » Sun, Jul 05, 2015, 6:13 PM UTC

dllthomas wrote: post #30

tel wrote: post #21

Earlier quoted context omitted.

Consider mtl then. It provides commutative capability set building semantics from the user's POV and then only asks the consumer to make final stack-ordering/effect specification decisions.

I find mtl pretty close to a sweet spot. The one thing I wish for is to be able to constrain effect order as a user (using your terminology above) when I'm writing code where one ordering or another is incorrect. The closest I can come is to fix the top of the stack, which suffices for correctness but puts some unnecessary burden on the consumer.

My solution is to make a new typeclass which implies the order you demand. It'll all be social contract driven, but until we have dependent types one cannot ask for more.

Re: Developing Web Applications with Haskell

#33

Post by dllthomas » Sun, Jul 05, 2015, 6:28 PM UTC

tel wrote: post #32

dllthomas wrote: post #30

Earlier quoted context omitted.

I find mtl pretty close to a sweet spot. The one thing I wish for is to be able to constrain effect order as a user (using your terminology above) when I'm writing code where one ordering or another is incorrect. The closest I can come is to fix the top of the stack, which suffices for correctness but puts some unnecessary burden on the consumer.

My solution is to make a new typeclass which implies the order you demand. It'll all be social contract driven, but until we have dependent types one cannot ask for more.

Ah, good call!