3 ms·

I couldn't disagree more. Nix doesn't make development easier. In fact, it substantially complicates development to ease open source delivery and client depende

I couldn't disagree more. Nix doesn't make development easier. In fact, it substantially complicates development to ease open source delivery and client dependency management. These are things that are of questionable value to the Haskell or product dev ecosystem, as people far more often prefer fully static (admittedly large) binaries anyways. And, Nix doesn't work well with existing tools like intero, it requires troubleshooting to get working with ghc. You can pick either stack or cabal and both sort of support Nix, but in every case some tooling will not quite work right. Further, if you're not doing 100% open development, Nix's delivery story is also complicated. It's further challenged for projects using private docker or GitHub repos, where in many cases there is simply no support in Nix. No one does Haskell newbies any favors by suggesting they learn a whole new package expression language and toolchain (that they will be interacting with deeply and constantly) in addition to a language that is full of fundamentally novel concepts and a vast breadth of new libraries, techniques, and a distributed documentation style. Please. Stop recommending Nix to new Haskell users until at least the new porcelain commands are shipped.

danharaj 9y ago
I didn't, at all, recommend nix to anybody. What are you responding to?
- garmaine 9y ago
  > Haskell + Nix is the best environment I've ever used for any development That sounds like a recommendation.
  - ianai 9y ago
    for developing haskell
  - danharaj 9y ago
    That's because it's spefically optimized for my needs: writing Reflex apps. It's what I do for a living. Everyone has different priorities. I know some users who started using Haskell at all with reflex-platform despite the difficulty because it scratched exactly their itch.
    - KirinDave 9y ago
      Well, as complex as Nix+whatever-you-have-cobbled-together-to-build-and-editor-instrument-ghcjs is, it pales in comparison to the sheer ferocious confusion granted to the ecosystem by tools like webpack, so I can see where it might seem like an improvement in some regards. Webpack: it's like lens error messages for your builds, at runtime!
- KirinDave 9y ago
  It sure read like that to me, but given the international nature of this forum, I'll take you at your word. Nor do I disagree with you about your assessment of your experience. But your experience and your requirements differ from mine, and in a professional capacity I could never recommend Nix for an organization.

danharaj 9y ago

I didn't, at all, recommend nix to anybody. What are you responding to?

garmaine 9y ago
> Haskell + Nix is the best environment I've ever used for any development That sounds like a recommendation.
- ianai 9y ago
  for developing haskell
- danharaj 9y ago
  That's because it's spefically optimized for my needs: writing Reflex apps. It's what I do for a living. Everyone has different priorities. I know some users who started using Haskell at all with reflex-platform despite the difficulty because it scratched exactly their itch.
  - KirinDave 9y ago
    Well, as complex as Nix+whatever-you-have-cobbled-together-to-build-and-editor-instrument-ghcjs is, it pales in comparison to the sheer ferocious confusion granted to the ecosystem by tools like webpack, so I can see where it might seem like an improvement in some regards. Webpack: it's like lens error messages for your builds, at runtime!
KirinDave 9y ago
It sure read like that to me, but given the international nature of this forum, I'll take you at your word. Nor do I disagree with you about your assessment of your experience. But your experience and your requirements differ from mine, and in a professional capacity I could never recommend Nix for an organization.