binaryen VS scotty

I've encountered a building problem when using asterius to compile a multi-packages cabal project, the detail could be found here, any suggestions?

ghcjs is the way to go for you, and soon it might be asterius. i do not know how hard it is to set ghcjs up without a framework. but frameworks like obelisk (based on reflex-dom), shpadoinkle, and miso automate that for. i personally like obelisk for its functional reactive programming but it can get awkward and get in your way. so if gui programming is just a means to the end of this one small application and you are not really interested in it nor functional reactive programming, shpadoinkle or miso might suit you better. miso implements the elm architecture (also "TEA", "functional model view controller") and shpadoinkle implements something directly equivalent to the elm architecture. but shpadoinkle achieves more composable widgets by minimalizing the elm architecture. so i recommend shpadoinkle for its better concept although miso is more mature.

Also, hint uses unsafeCoerce, and thus implicitly relies on an assumption about how values are represented at runtime. Namely, if a program P is interpreting an expression E of type A, hint assumes that the value of type A produced by the ghc interpreter has the same representation as the values of type A which are manipulated by program P. This is not guaranteed to be the case, since P has been compiled by the compiler portion of ghc while E has been evaluated by the interpreter portion of ghc. This means the ghc devs had to carefully craft their compiler and interpreters to match. When targetting the browser, a Haskell-to-js or Haskell-to-wasm compiler such as Asterius modifies ghc's code-generator so it produces js or wasm code. You would thus also need to tweak the interpreter so that it produces js or wasm values which match what the modified code-generator outputs. Or you could restrict yourself to the hint's less expressive eval :: String -> String API.

We found a post where someone had a similar issue (here), but the fix in that issue doesn't help: using `ar` from `binutils` causes link errors like this instead:

https://github.com/tweag/asterius/issues/851 (asterius has a demo, but no source, and I -assume no lua filter support)

All modern ones support Haskell: https://github.com/tweag/asterius

Another option is Asterius. I'm not familiar with the current state, and it's not had active development for about 3 months now, either, so it may be in the same boat? But I think the big disadvantage of Asterius is that there's just a lot less usage, and therefore a lot less testing with the whole Haskell ecosystem, versus GHCJS which has been a fixture for a while and where loads of people have thought about compatibility for years.

Check out asterius

I've played around with Haskell via the Asteruis project : https://github.com/tweag/asterius

Also emscripten of course, for C/C++.

I would suggest checking out scotty for the http server - it uses warp by default, and is very beginner-friendly.

Here's the current commit I'm working with: https://github.com/scotty-web/scotty/commit/3ed8586c046b46dc42740e8ac2e7fe712e84191d

If you're not a fan of the ruby-on-rails / swiss army knife approach that IHP takes, check out Scotty. Add Lucid for Html rendering, and Selda for Postgres. (There are other options for any of these tools if you prefer)

- Scotty (simple web routing) https://hackage.haskell.org/package/scotty

Writing a Haskell webserver (maybe using scotty) and call it from node.

I've been looking for this as well, and found the globalstate.hs example in the scotty github repository. It uses a ReaderT of a TVar and shows how to update or read shared state in memory.

I've found htmx and hyperscript talking to scotty to be an easy way to get something like this going while retaining the joys of Haskell on the backend and avoiding the pains of Haskell on the frontend.

Finally, to add my opinion in the context of some other posts: I'd suggest Scotty (and probably other libraries I'm less familiar with) before Servant in particular, as Servant is a lot to absorb if you're also trying to build fluency in Haskell at the same time. Similarly, I'd advocate for Elmish (disclaimer, it's written by (very talented programmers other than myself at) my company) over Halogen, at least based on the last time I tried Halogen--I found it pretty complex as well. Don't get me wrong, I think Servant and Halogen are both great, just...complex.

This is an example of REST API built with Scotty a web framework of Haskell and PostgreSQL a relational database. It's a simple API to manage products.

Not that I'm much of an expert, but if you're talking about a very barebones static single-page-app, then you could very easily get by just using blaze-html to put your elements on the page, and then scotty is a basic web framework you could use to serve up your app.