4 ms·

As a * nix geek it's beneath his station. Welcome to the flip side of the academic ivory tower, the scoff at academic stuff because it doesn't "get shit done".

• k_bx 11y ago
  It does "get shit done" for us perfectly, and type-system only helps here. So I still don't see why it's not suitable for *nix geeks. Give it a try!
  • saurik 11y ago
    I read Dewie3's comment as agreeing with you, albeit via sarcasm and cynicism (and some negativity).
    • Dewie3 11y ago
      Right you are. I'm here all night.
  • f0nd004u 11y ago
    Try building a package with Haskell dependencies for a linux distribution sometime. It is horrifying.
    • codygman 11y ago
      Just built my project on NixOS with no problems. Built it on Ubuntu with a cabal sandbox, no problems. Using stackage LTS I have no problems. Built it using Halcyon as well. Building with vanilla cabal I might have some issues, but professional haskeller's use the tools mentioned above.
    • k_bx 11y ago
      It's not with stackage. You just do pre-setup: cabal update && cabal install stackage Building project: 1. clone a project, cd into it 2. stackage sandbox init 3. cabal install --only-dependencies 4. cabal configure && cabal build If you already used some "lts version", you can put "stackage sandbox init lts-2.4" to second command and it will re-use existing lts-2.4 sandbox without a need to reinstall anything. That's it. It takes a very long time first time you build with this with some version of lts stackage, and there is some movements towards binary package sets, but I'm not sure on status of that.
      • snikch 11y ago
        IMO this sums up one of the biggest benefits with Go, and unfortunately goes against your own point. There's no need to know about a variety of community built tools, or what's the "best solution" in language X - the std lib gives you what you need. You can stand up a service quickly because it's simple, and there's no "in knowledge" required.