4 ms·

I tried out Yesod and Snap a while back and while the frameworks themselves were pleasant to work with from what I could tell, I spent whole days messing with p

by 3131s 9y ago

I tried out Yesod and Snap a while back and while the frameworks themselves were pleasant to work with from what I could tell, I spent whole days messing with package management issues that would render my projects unrunnable after new installs. I couldn't see myself working with Haskell in production for a web project until that situation improves.

fasquoika 9y ago
Aren't some Haskell developers also using Nix for dependency management?
- tikhonj 9y ago
  I use Nix and it's awesome, but still in early adopter territory. It works wonderfully if you really value reproducible builds and are willing to put some effort in the initial setup, but it's still a bit fiddly and documentation is nearly non-existent. If you have the time and motivation to learn about it up-front and get it set up it pays off, but I wouldn't recommend it to beginners just trying to learn Haskell.
platz 9y ago
How long is a while back?
- 3131s 9y ago
  A couple months ago. I'll definitely give them another shot, but it was very non-exotic stuff like installing snaplet-postgresql-simple that sent two separate systems into dependency hell.
  - platz 9y ago
    That's pretty recent. I'm sure you're aware of stack , solves most 'dependency hell' issues. I'm not sure how much snap is maintained these days BTW, but definitely yesod is actively maintained and should have no dep issues there especially if using stack
    - jfoutz 9y ago
      My limited understanding is if I require a package ‘A’ and another package ‘B’ it’s fine. Unless ‘A’ depends on a different ‘B’. Then I’m pretty much fucked.
      - platz 9y ago
        Thats is what stack solves
zzzzzzzza 9y ago
Funny I do web dev, mostly haskell and javascript and feel like haskell is a solid rock and javascript is unbearable. Part of the explanation may be ease of initial interchangeability (javascript: oh yeah we can glue that to this no problem, it's all just like json or whatever man) versus maintainability (haskell: here is your type contract, the closest thing you can get in code to the fundamentalness and immutability of 2+2 =4).

by 3131s 9y ago

fasquoika 9y ago

Aren't some Haskell developers also using Nix for dependency management?

tikhonj 9y ago
I use Nix and it's awesome, but still in early adopter territory. It works wonderfully if you really value reproducible builds and are willing to put some effort in the initial setup, but it's still a bit fiddly and documentation is nearly non-existent. If you have the time and motivation to learn about it up-front and get it set up it pays off, but I wouldn't recommend it to beginners just trying to learn Haskell.

platz 9y ago

How long is a while back?

3131s 9y ago
A couple months ago. I'll definitely give them another shot, but it was very non-exotic stuff like installing snaplet-postgresql-simple that sent two separate systems into dependency hell.
- platz 9y ago
  That's pretty recent. I'm sure you're aware of stack , solves most 'dependency hell' issues. I'm not sure how much snap is maintained these days BTW, but definitely yesod is actively maintained and should have no dep issues there especially if using stack
  - jfoutz 9y ago
    My limited understanding is if I require a package ‘A’ and another package ‘B’ it’s fine. Unless ‘A’ depends on a different ‘B’. Then I’m pretty much fucked.
    - platz 9y ago
      Thats is what stack solves

zzzzzzzza 9y ago

Funny I do web dev, mostly haskell and javascript and feel like haskell is a solid rock and javascript is unbearable. Part of the explanation may be ease of initial interchangeability (javascript: oh yeah we can glue that to this no problem, it's all just like json or whatever man) versus maintainability (haskell: here is your type contract, the closest thing you can get in code to the fundamentalness and immutability of 2+2 =4).