eff VS ihp

There are also a few subtle issues that arise with delconts related to semantics of higher order effects (see here and here), but they might be solvable.

Details are in https://github.com/hasura/eff/issues/12 and https://www.reddit.com/r/haskell/comments/pywuqg/unresolved_challenges_of_scoped_effects_and_what/.

You'll get fearless parallel with STM in the mixture, and GHC is getting a work in progress effect system for Haskell, as Delimited continuation primops has been merged.

My last example is algebraic effects, some of which have been made possible in a both practical and efficient way thanks to extremely recent research, and that I can use to implement architectures like Ports and Adapters or Clean Architecture and have very maintainable code. (Extensible Effects — An Alternative to Monad Transformers was published in 2013, Effect Handlers in Scope was published in 2014 and they are behind Polysemy, while there is ongoing work on effects with even better performance, like Eff)

cleff's Eff monad is esentially implemented as a ReaderT IO. [...] This is first done by eff, [...]

Here is link number 1 - Previous text "eff"

This is essentially how continuation based effect systems work, check out eveff and eff.

Languages such as Koka only support algebraic effects, not scoping operations such as catch and listen. The Effect Handlers in Scope paper introduces scoping operations, which lead to the Haskell libraries fused-effects and polysemy, but they turned out to have some weird semantics. eff is her effort to fix that.

While her eff is still under construction, there are relative more mature pieces like Koka etc. I'd very much like to understand how her concerns map to those other effect systems, but can't find more write-ups about the design space of effect systems.

Let me tell you what I'm worried about with effects systems: One of the smartest people I know of has a library called Eff https://github.com/hasura/eff that efficiently implements effects through some modifications to GHC. The thing is, she's pretty much stopped working on because she found some really nasty semantic edge-cases that she couldn't resolve to her satisfaction. (I don't understand the problems well enough to describe them, and I think they're specific to lazy languages, but it has left me cautious about the effect model in general.)

You could contribute to IHP! We have some great docs to get started here https://github.com/digitallyinduced/ihp/blob/master/CONTRIBUTING.md And we have some low hanging fruits in GitHub issues for you to get started with, e.g. https://github.com/digitallyinduced/ihp/issues/1601 (also there's always lots of activity in the IHP Slack, in case you have any questions/need help)

Really happy we've finally go to the 1.0 status :) If you like to take a look at the code, check our GitHub at https://github.com/digitallyinduced/ihp

kinda early for running roc in production perhaps, but you can try out haskell and its frameworks like ihp or some other web / mobile / multiplatform framework.

In recent years the Haskell ecosystem has drastically improved.

With Haskell Language Server (HLS) there's now great autocompletion and inline error reporting for e.g. VSCode and other editors.

We've recently got dot-notation, so you can type `myRecord.myField` instead of `myField myRecord`, which makes Haskell code feel more familiar when switching from other languages.

With IHP we now even have a Haskell version of Rails/Laravel. Check it out here: https://ihp.digitallyinduced.com/ (I'm founder of IHP)

Yes, it's possible to build a traditional web company with Haskell. We've made IHP exactly for that :) It's like Rails/Django but for Haskell. https://ihp.digitallyinduced.com/ We specifically try to be batteries-includes (like rails), so you don't have to think too much about what libraries to use, the core of IHP can get you very far without needing to manually decide between libraries.

IHP even won a G2 badge, which is kind of funny and ironic for a Haskell project :D https://www.g2.com/products/ihp/reviews

Thanks to reintroduction of deep subsumption we could finally update IHP to the GHC 9 series. So really happy about the recent GHC releases :)

If you're curious about Haskell, IHP is a good starting point (https://ihp.digitallyinduced.com/ https://github.com/digitallyinduced/ihp). IHP is Haskell's version of Laravel/Rails/Django. It's really a superpower to have Haskell's type system combined with the rapid development approach of Rails :) (Disclaimer: I'm founder of the company that makes IHP)

Check out IHP. Compared to Yesod it's a bit more opinionated. This might be a useful, as it allows you to focus on your domain problem instead of picking libraries etc. Also we have a very active Slack community with over 350 Haskellers. If you have any questions, you can always get help on slack.

IHP might be worth checking out. It's very batteries-included, a little like Ruby on Rails. It has very good developer tooling too, imo. It does encourage you to write some kind of non-standard Haskell, but it's minor enough that it's not a big deal.